I have packaged and released version 0.2.3 of gerald. This is mainly a tidy up and bug fix release, with numerous additional unit tests. You can find all of the details in the CHANGELOG.txt file that comes with the source distribution (or view it here) but in a nutshell the changes from the last release are;
- Numerous renames to more fully comply with PEP-8
- Added numerous tests, full details in the CHANGELOG.txt file
- Added an ‘enabled’ flag to table constraints (except in the MySQL module, because that database doesn’t support them)
- Added support for column defaults in Oracle
- Added a ‘table_name’ attribute to the schema.Trigger class
- Removed main and usage functions from each module that shouldn’t be imported
Please download, install and enjoy. Bug reports or tumultuous praise to the usual address please.
Catching up on my blog reading I notice that Mark Rittman is down under next week. I’m not in a position to attend but if you are working in the Oracle and BI world you shouldn’t miss this seminar from a truly world class expert in all things Oracle and BI.
And Mark, there is an offer of a cold beer on your blog.
The latest release of SQL Developer slipped out yesterday.
I’ve been trying the pre-release version and its starting to become a really useful tool. My copy of 1.1 final is downloading as I type.
Update: When I got to work this morning I tried automatically updating the copy of 1.0 on my work machine. It doesn’t appear to work. It looks like you have to download a copy of 1.1 and install it yourself.
The admonition (since the Oracle 6 days if my memory serves) for good DBAs is to never use the default roles when granting privileges to users in Oracle databases. Always grant users the specific privileges they require and never rely on ‘CONNECT’ or ‘RESOURCE’, because they generally grant more rights than you really want.
Oracle seems to have addressed this in 10g2, at least according to this this blog post and my observation. Now, granting the ‘CONNECT’ role is exactly the same as explicitly granting the ‘CREATE SESSION’ privilege and the ‘RESOURCE’ role has a more reasonable list of privileges.
I’d still be wary of them though, because through sheer laziness I granted these roles to a user in my development database and then got an ORA-01031 error when I tried to create a view. That’s right, the ‘RESOURCE’ role doesn’t (and as far as I can tell never did) contain the privilege to create a view. How strange.
So this advice would appear to still be valid - only grant those privileges that your users need and do it explicitly.