Subject | Logging Patches to Database |
---|---|
Author | inoffensive_2009 |
Post date | 2009-02-26T06:44:08Z |
Hi Folks:
In a thread the other day, Adam told me he keeps a table that
tracks patches to the database, so he knows what's been applied.
I've been testing the database to see if a new table, or column
exists, or a column has the correct width, and applying a particular
create a table, or alter a table, if the query indicates that the DB
isn't current.
I don't know how expensive it is to perform these queries, but I'm
interested in how you folks are logging your patches.
Do you have a table that describes has a version number, and know
what patches need to be applied to get that current? Or do you have a
column for each change to the database like "CONTACT_ZIP_EXPANDED",
"WEB_ADDRESS_TABLE_ADDED".
Or is there a whole different approach that makes more sense.
Thanks
Larry
In a thread the other day, Adam told me he keeps a table that
tracks patches to the database, so he knows what's been applied.
I've been testing the database to see if a new table, or column
exists, or a column has the correct width, and applying a particular
create a table, or alter a table, if the query indicates that the DB
isn't current.
I don't know how expensive it is to perform these queries, but I'm
interested in how you folks are logging your patches.
Do you have a table that describes has a version number, and know
what patches need to be applied to get that current? Or do you have a
column for each change to the database like "CONTACT_ZIP_EXPANDED",
"WEB_ADDRESS_TABLE_ADDED".
Or is there a whole different approach that makes more sense.
Thanks
Larry