Add files via upload - #62
Conversation
upgrade to v2.1.0 from the previous release
sql-williamd
left a comment
There was a problem hiding this comment.
Thanks for this idea. We'd been thinking about how to implement this (or even if we should).
Enrico and I think it is probably easiest to create an upgrade file for each release, named for the release.
We are thinking of making a PowerShell upgrader (like the install and uninstall), which will deal with these files correctly.
For now, this is a great addition!
I've added thoughts/revision requests in this PR. If you have questions, just drop me a message here.
| EXEC sys.sp_addextendedproperty @name=N'oqs_version', @value=N'2.1.0' , @level0type=N'SCHEMA',@level0name=N'oqs', @level1type=N'TABLE',@level1name=N'collection_metadata' | ||
| GO | ||
|
|
||
| DELETE FROM [oqs].[collection_metadata] |
There was a problem hiding this comment.
We'd like to keep metadata between upgrades. Can you "archive" the settings before making the change, then re-insert them, adding the new column values to it. This way, OQS behaviour remains the same for a user between versions.
| USE $(DatabaseWhereOQSIsRunning) | ||
| GO | ||
|
|
||
| ALTER TABLE [oqs].[collection_metadata] |
There was a problem hiding this comment.
I love the default idea here..... i think we should add that to the general installer.... (i've just made an issue for that reason)
| [data_cleanup_threshold], | ||
| [data_cleanup_throttle] | ||
| ) | ||
| VALUES ( N'EXEC [oqs].[gather_statistics] @logmode=1', 60 , '$(OQSMode)','$(DatabaseWhereOQSIsRunning)',1,2,0,30,5000); |
There was a problem hiding this comment.
with the default constraints done on the entire table, we can just insert DEFAULT VALUES here. makes it cleaner.
|
Things have moved on quite a bit since this PR was submitted. I'm closing this now, if you want to resubmit based on a newer version, please do so |
upgrade to v2.1.0 from the previous release