I spotted this today and couldnt resist talking about it. I was reading Eric Burke's comic look at typical product masters and looking inwardly at our own products. Most of the 'Walk up and use' products are things like the iPod, the toaster and other.
Avoiding the 'me too' scenario is going against the grain in many places. For SQL Developer, we have tried to keep the amount of functionality exposed as clear and simple as possible.
In 2.1 we have pushed a lot of the added functionality down into menus which do not need to be used all the time. We have simplified the number of dockables that we start and made a lot of the basic functionality of the navigator, worksheet and data management much cleaner and simpler.
We're getting ready to cut a release candidate so you should check it out for yourself.
Testing. When you're writing code, how often do you test it? Ok, you test it, but how often do you spend the time to put a set of discrete tests together to make sure that your code is doing what you thought it would do and moreover, it doesnt do what its not supposed to.
As part of SQL Developer 2.1, Unit Testing is one of the main features we have added. This is very different to anything you've seen in this area before. There are 5 different things on the new navigator we have added.
Tests: These are individual or discreate tests against a piece of code like a stored procedure or a function or package. Each test can have several implementations of the test. I.e., if it is a stored procedure, you can have an implementation with n implementation depending on the permutations of the paramters that you want to support.
Suites: This is a regular concept, like JUnit, which you can use to group your tests and run them together, in sequence. In fact, with 2.1, you can run unit tests from the command line which means you can hook them up with your build machine and run these in as part of a standard build and publish results with your builds
reports: We have canned several reports so you can see how your suite of tests ran, what the coverage numbers are and allow you to drill through each implementation that was run.
Lookups: Lookups are setup to allow you to predefine static parameter values that can be group by functional need and used in test implementations.
Libraries: Like the word says, these are libraries of startups, teardowns, validations, and defined dynamic values that we want to use regularly in tests.
The test here shows each implementation of the test. The implementation is a set of parameters which will give you a specific result, based on processing the parameters as part of the stored procedure.
This is our first release of Unit Testing and we will add more features in the next few releases. This release allows you to set up suites of tests with parameters covered by all the scalar datatypes. We will cover more abstract types in future releases.
This is available as part of SQL Developer 2.1, which at time of writing this is available as an EA from http://otn.oracle.com/sqldeveloper. Download it and play with it. If there are things you like, let us know and if there are things you would like added, then you can let us know on the feature request page as usual which is http://sqldeveloper.oracle.com
Sue has kicked off open world introducing SqlDeveloper 2.1. You should check it out on http://sqldeveloper.oracle.com . If you're around openworld tomorrow, you need to check out Kris Rice's talk on Unit testing. It's new, different and really cool!
So, ok, whats weird or unusual about this setup you ask? Speed. The database and apex responses are instant on the macbook pro, and when I'm done I can export the app and deploy it on apex.oracle.com to share it with other folks.
Working through the last issues with SQL Developer 1.5.4. We've done a lot of work with this to address functionality that people required in the base product and now have translated it to 9 languages.
Once we are happy with the current builds, we'll be out to users as soon as we can. I also hope that this is the version to be adopted in the Oracle Database 11GR2 database
Oracle SQL Developer Data Modelling is the latest product offering to join our Oracle Database Tools. SQL Developer Data Modelling has Entity Relationship modeling, Relational (Database Design), Data Type and Multidimensional modeling, full forward and reverse engineering and code generation. It includes importing from and exporting to a variety of sources and targets, provides a variety of formatting options and validates the models through a predefined set of Design Rules. All in all, fills in one of last pieces of the database development cycle allowing us to model our databases before we go ahead and physically lay them out and create them. My personal favourite is the multidimensional modelling features.
Years ago, I was involved in a huge implementation of a warehouse which was all defined by hand; the fact tables, the dimensions and all the aggregates. This was fine at the time, but being able to go the database and extract the structure of it and show it as a model would have been great. Have a look at the image and the way the fact, dimension and aggregate objects are laid out.
Anyway, the talk today was great with loads of questions around how we'd handle Designer, Erwin and other formats, and why we just didn't use Rational or JDeveloper. There are a lot of answers for this in the FAQ.
For now, we have a couple more hands on labs where the attendees can get their hands on the software and ask questions about what they are doing.
Download it and try it and if you have questions, ping the forums and we'll help you get going.
After several days of visa processing, I'm clear to go to Moscow. Spasiba Mockba! I'm speaking on Wednesday 4th on our new data modeling tools. I'm hoping to go through a presentation of the features by demo on the fourth starting with a reverse engineering of a couple of schema to a relational model and abstracting that into a logical model. I want to show several views and slices of the model. I also want to show a load of the property management capabilities such as naming conventions to constrain object names. From there, we can push down and create a physical model, containing the attributes of that model, such as tablespaces, indices and multi dimensional objects. Lastly, We'll complete the circle and do some DDL Generation. On Thursday, I have set up two hands-on labs to allow attendees to work through a prescribed text showing much of the same features I'll discuss in the talk. Technorati Tags: Oracle Develop, SQL Developer, Modeling
After a great holiday season, its time to get back to the grindstone. We released SQL Developer 1.5.3 before Christmas which is our first translated release. Its just japanese right now and we'll be extending that to nine languages in 1.5.4. The other major part of 1.5.4 I want to sweep up are as many issues as possible from our customers on the forums. Over the next few weeks, we'll be focusing on locking down as many of these as possible. In terms of conferences, I'm off to Moscow in February as part of the series of Oracle Develop conferences. I'll be doing a couple of sessions on SQL Developer and hope to get under the covers to show exactly how you can build your own additions to it. I was watching Sue present at UKOUG and it was the one thing that struck me that people were looking for as heads were bobbing around the room.