Comments
Sort by recent activity
It would be nice if the static data support is added to the product. Also, it would be nice if it was possible to choose which part of the static data should go under source control.
For example,
Data that comes with default installation of my program should be source controled but the data that developer inserts through the program to check his work should not. Basically, if the data is inserted/updated/deleted from ssms then it should be in source control otherwise it should not. It would be nice if you included similar feature in the program. / comments
It would be nice if the static data support is added to the product. Also, it would be nice if it was possible to choose which part of the static data should go under source control.
For example,
D...
I guess I didn't explain it well.
There is two kinds of static data in the database:
1. The static part of the data that comes with the installation and cannot be edited/added/deleted by the user. This should be in source control. If the developer makes changes to the data with ssms it should be reflected in source control. It can be solved with sql data compare as it is possible to limit what to synchronize
2. Preconfigured values that can be changed. For example default data for a dropdownbox. The user can add/edit/delete data from the program.
This should be in source control. However when a developer modifies some data to it through the program it shouldn't go in source control. A possible solution can be to have a isdefault column which distinguishes between default and user data. The problem with this approach is that if preconfigured record is modified or deleted from the program (so isdefault is true) it should not be changed in the source control.
Thanks. / comments
I guess I didn't explain it well.
There is two kinds of static data in the database:
1. The static part of the data that comes with the installation and cannot be edited/added/deleted by the user. ...