Issues with new tables with data and new table columns
jmavis
Posts: 2
I've found two issues using Packager to create an upgrade script and was wondering if there's a workaround:
-Create two databases (ONE and TWO).
-Create a table called NewColumn in both and add the same data to them.
-Append a new column on the NewColumn table in TWO and add data for that column to the existing rows.
-Create a table called NewTable in TWO and add data to it.
Now, when I create an upgrade script from ONE to TWO:
-It will do the schema for NewTable, but it doesn't do the data.
-It will do the column for NewColumn, but it doesn't update the data.
Thanks.
-Create two databases (ONE and TWO).
-Create a table called NewColumn in both and add the same data to them.
-Append a new column on the NewColumn table in TWO and add data for that column to the existing rows.
-Create a table called NewTable in TWO and add data to it.
Now, when I create an upgrade script from ONE to TWO:
-It will do the schema for NewTable, but it doesn't do the data.
-It will do the column for NewColumn, but it doesn't update the data.
Thanks.
This discussion has been closed.
Comments
This is something that we are working on fixing. Basically, SQL Packager needs to find the differences in data between two tables to script the data in an upgrade package, and it can't do this if the table doesn't exist in the database to be upgraded.
The workaround is to create a separate schema and data package.