It's Rockin' Awesome.
I went to the ODTUG presentations that Sue Harper did on SQLDeveloper and was very impressed with some of the features that I didn't know about and also the stuff that is on its way.
When she showed how to import data from Excel (ok, it is broken in the current patch, but it rocks) and then showed the Normalize feature, I was blown away.
Combine that with the upcoming (unofficial) Data ing tool (which I've been previewing/using in the JDeveloper 11g technical preview), and I'm ready to throw away Designer. No offense, but currently, we use Designer for very little. I've built separate scripts to take care of building audit columns. I need to build a script that will build a Journal table and then I'll be done with Designer forever, since we were really only using it for ing and the auditing/journaling API's that id built.
It also inspired me. Between APEX and SQLDeveloper, there is NO reason to create data and maintain business-critical in Excel. Now, Excel becomes just another output method in my opinion. And Word -- seriously, I'm blown away that anyone would store data in Word. Word is a great Word Processor, not a data storage system.
I love that Code Templates and configurable Tab sizes are available in the newer versions of SQLDeveloper. Those were among my two biggest complaints about a year ago. Petty, I know, but Code Templates are such a huge time-saver. I mean, there are certain things you do as a developer thousands of times in your career. If you hand-type them every time, then you are 1) Dumb, and 2) Going to forget something and build a bug.
I went to the ODTUG presentations that Sue Harper did on SQLDeveloper and was very impressed with some of the features that I didn't know about and also the stuff that is on its way.
When she showed how to import data from Excel (ok, it is broken in the current patch, but it rocks) and then showed the Normalize feature, I was blown away.
Combine that with the upcoming (unofficial) Data ing tool (which I've been previewing/using in the JDeveloper 11g technical preview), and I'm ready to throw away Designer. No offense, but currently, we use Designer for very little. I've built separate scripts to take care of building audit columns. I need to build a script that will build a Journal table and then I'll be done with Designer forever, since we were really only using it for ing and the auditing/journaling API's that id built.
It also inspired me. Between APEX and SQLDeveloper, there is NO reason to create data and maintain business-critical in Excel. Now, Excel becomes just another output method in my opinion. And Word -- seriously, I'm blown away that anyone would store data in Word. Word is a great Word Processor, not a data storage system.
I love that Code Templates and configurable Tab sizes are available in the newer versions of SQLDeveloper. Those were among my two biggest complaints about a year ago. Petty, I know, but Code Templates are such a huge time-saver. I mean, there are certain things you do as a developer thousands of times in your career. If you hand-type them every time, then you are 1) Dumb, and 2) Going to forget something and build a bug.
No comments:
Post a Comment