Developing Schema Compare for Oracle (Part 4): Script Configuration
Posted
by Simon Cooper
on Simple Talk
See other posts from Simple Talk
or by Simon Cooper
Published on Mon, 26 Apr 2010 11:42:00 GMT
Indexed on
2010/04/26
14:15 UTC
Read the original article
Hit count: 272
If you've had a chance to play around with the Schema Compare for Oracle beta, you may have come across this screen in the synchronization wizard:
This screen is one of the few screens that, along with the project configuration form, doesn't come from SQL Compare. This screen was designed to solve a couple of issues that, although aren't specific to Oracle, are much more of a problem than on SQL Server: Datatype conversions and NOT NULL columns.
1. Datatype conversions
SQL Server is generally quite forgiving when it comes to datatype conversions using ALTER TABLE
. For example, you can convert from a VARCHAR
to INT
using ALTER TABLE
as long as all the character values are parsable as integers. Oracle, on the other hand, only allows ALTER TABLE
conversions that don't change the internal data format. Essentially, every change that requires an actual datatype conversion has to be done using a rebuild with a conversion function.
That's OK, as we can simply hard-code the various conversion functions for the valid datatype conversions and insert those into the rebuild SELECT
list. However, as there always is with Oracle, there's a catch. Have a look at the NUMTODSINTERVAL function. As well as specifying the value (or column) to convert, you have to specify an interval_unit, which tells oracle how to interpret the input number. We can't hardcode a default for this parameter, as it is entirely dependent on the user's data context!
So, in order to convert NUMBER
to INTERVAL DAY TO SECOND
/INTERVAL YEAR TO MONTH
, we need to have feedback from the user as to what to put in this parameter while we're generating the sync script - this requires a new step in the engine action/script generation to insert these values into the script, as well as new UI to allow the user to specify these values in a sensible fashion.
In implementing the engine and UI infrastructure to allow this it made much more sense to implement it for any rebuild datatype conversion, not just NUMBER
to INTERVAL
s. For conversions which we can do, we pre-fill the 'value' box with the appropriate function from the documentation. The user can also type in arbitary SQL expressions, which allows the user to specify optional format parameters for the relevant conversion functions, or indeed call their own functions to convert between values that don't have a built-in conversion defined. As the value gets inserted as-is into the rebuild SELECT
list, any expression that is valid in that context can be specified as the conversion value.
2. NOT NULL columns
Another problem that is solved by the new step in the sync wizard is adding a NOT NULL column to a table. If the table contains data (as most database tables do), you can't just add a NOT NULL column, as Oracle doesn't know what value to put in the new column for existing rows - the DDL statement will fail. There are actually 3 separate scenarios for this problem that have separate solutions within the engine:
Adding a NOT NULL column to a table without a rebuild
Here, the workaround is to add a column default with an appropriate value to the column you're adding:
Note, however, there is something to bear in mind about this solution; once specified on a column, a default cannot be removed. To 'remove' a default from a column you change it to have a default of NULL, hence there's code in the engine to treat a NULL default the same as no default at all.ALTER TABLE tbl1 ADD newcol NUMBER DEFAULT <value> NOT NULL;
Adding a NOT NULL column to a table, where a separate change forced a table rebuild
Fortunately, in this case, a column default is not required - we can simply insert the default value into the rebuildSELECT
clause.Changing an existing NULL to a NOT NULL column
To implement this, we run anUPDATE
command before theALTER TABLE
to change all the NULLs in the column to the required default value.
For all three, we need some way of allowing the user to specify a default value to use instead of NULL; as this is essentially the same problem as datatype conversion (inserting values into the sync script), we can re-use the UI and engine implementation of datatype conversion values. We also provide the option to alter the new column to allow NULLs, or to ignore the problem completely.
Note that there is the same (long-running) problem in SQL Compare, but it is much more of an issue in Oracle as you cannot easily roll back executed DDL statements if the script fails at some point during execution. Furthermore, the engine of SQL Compare is far less conducive to inserting user-supplied values into the generated script. As we're writing the Schema Compare engine from scratch, we used what we learnt from the SQL Compare engine and designed it to be far more modular, which makes inserting procedures like this much easier.
© Simple Talk or respective owner