I created a simple Grails application which makes it possible to store client data inside a MySQL database. I created this application since I want to learn more about GORM (Grails Object Relational Mapping).
I already tested the application in the internal server from Grails, but I wanted to deploy it to a remote server. So I created a development account on Openshift and there I created the following server:
since we released our first preview of SDSQL, we've made a lot of changes to it and enhanced a lot of things too in there so it would be more useable. One specific one was the use of LDAP which some customers on SQLDeveloper are using in their organisations as a standard and our first release precluded them from working with this.
Well, to add this, we wanted a way that we could specify the LDAP strings and then use them in a connect statement. We introduced a command called SET LDAPCON for setting the LDAP connection. You can set it like this at the SQL> prompt
Ever want to run a Stored Procedure or a PL/SQL anonymous block and just want to "print out" the results of a query ? Even as a little bit of debug information?
In Oracle 11g you have to create a SQL*Plus REFCURSOR variable and then bind it within the anonymous block or pass it as an argument to a procedure/function. Run the code and then print the refcursor.
This requires a bit of know how in SQL*Plus and how it will work with your PL/SQL block or procedure.
In SQL Developer, Jeff has shown in many tips & tricks talks and here on his blog how to get data from any select into a few formats. The most common I would say is csv. Nothing here has changed. Well, almost. What will be new is the html format is getting a facelift and a json format is being added neither are in the version of sdsql or sql developer that are on otn yet
This is in the process of evolving but should be enough for anyone to give it a whirl. The idea is that for any given statement you may want to run something before and possible after.
Here's a trivial example. I'm issuing 2 statements 1) a drop table and 2) creating a table of select * from v$mystat before each command. Then after I'm doing sql that shows me the changes from that point
First, we just put up a new build of sdsql. Go get it or the last thing here will not work.
SQL is a great and verbose language so there's many ways to shorten what we have to type. As simple as a view or saving a script to call later with @/path/to/sessions.sql SDSQL is taking it a step further and we added aliases to the tool. Almost as if right on queue, John asked if we could add them.
SQL Developer is now up to version 4.1 and has had many additions over the years to beef up the sqlplus compatibility. This is used today by millions of users adding up to millions if not billions of hours in the tool doing their work. That means our support of core sqlplus has to be very full featured. One idea we kicked around for a while but never had the time to do was to make our
Writing sql or any code is an iterative process. Most of the time that means to see what you have done say 5 minutes ago means how big is your undo buffer or better is if you are in SQL Developer there's a full blown history. If you are in sqlplus, you are basically out of luck.
SDSQL has built in history and between sessions. We are still jiggling where it stores the history so
Getting ddl out for any object is quite simple. You can just call dbms_metadata with something nice and easy like select dbms_metata.get_ddl('TABLE','EMP') from dual;
SQL> select dbms_metadata.get_ddl('TABLE','EMP') from dual;
CREATE TABLE "KLRICE"."EMP"
( "EMPNO" NUMBER