Comments
3 comments
-
Thank for your post into the forum.
I have added your suggestions to an existing Feature Request created regarding the same topic. The reference for this feature request is SC-1428.
Hopefully you will see the requested feature in a future version of SQL Compare.
Many Thanks
Eddie -
SQL Compare and SQL Source Control can now work side by side to achieve what you describe. You can commit your own custom script to source control (in this case you would add the UPDATE statement) and SQL Compare would be able to reuse this script in future deployments.
For more information visit:
http://www.red-gate.com/MessageBoard/vi ... 1312#51312
David Atkinson
Product Manager
Red Gate Software -
Interestingly, I’ve seen similar discussions about handling constraints and data changes while writing about different systems and updates in gaming communities as well. For example, when explaining new features and changes for custom servers like Null’s Brawl (especially the Pierce & Glowbert update), we also emphasize how certain settings or defaults affect the overall behavior of the system. I covered some details about that update here!
It’s always interesting how both database design and game server configurations rely on clear defaults and constraints to avoid unexpected behavior.
Add comment
Please sign in to leave a comment.
As you can see, Field2 can be NULL and we also have values in the database which are NULL. But because of new specifications or whatever, we need the table like this:
So, for an update, you need to recreate the table. SQL Server Management Studio makes something like this:
And here is the problem. You cannot insert the values into Tmp_Test, because Field2 does not allow NULL values anymore. But it would be possible, if you would turn the NULL-Value into the Default-Value, for example
I know, it is easy to workaround this, with a simple Update-Command before Updating
But perhaps it is worth some consideration to implement this feature.
Thank you,
Michael Kriegner