I routinely have a scenario where I need to add a column to a table,
populate the column with data and then set the column to not null. This
would be simple enough if the table were small, but I'm dealing with a
multi-TB data warehouse. What I currently do is add the column, split
up the work to
ibase-user@lists.sourceforge.net
Subject: [Liquibase-user] staging DB changes
I routinely have a scenario where I need to add a column to a table,
populate the column with data and then set the column to not null. This
would be simple enough if the table were small, but I'm dealing with
ril 01, 2009 2:03 PM
To: liquibase-user@lists.sourceforge.net
Subject: [Liquibase-user] staging DB changes
I routinely have a scenario where I need to add a column to a table,
populate the column with data and then set the column to not null. This
would be simple enough if the table were small,
ilto:bszal...@cobaltgroup.com]
Sent: Wednesday, April 01, 2009 4:24 PM
To: liquibase-user@lists.sourceforge.net
Subject: Re: [Liquibase-user] staging DB changes
We run an Oracle shop, so I end up using the Oracle Job queue to handle
the work. During deployment, the first stage does the DDL and submits
