I've looked through the archives and didn't see anything about this but if I missed it, please point me in the right direction.
The app I'm working on requires unattended updates whenever there is a new version available. Although it has been a big priority to crystallize the schema, I can't rule out the possibility of a schema change at some point. My plan to handle this is essentially to keep track of what version of the schema the db is using and package updates with incremental SQL scripts to update it. Before I get into this, is there anything I should watch out for? Is there a better way of doing it? Will I be able to execute the scripts through the .NET provider or will I need to shell out to isql? I guess I'm not really sure what sort of restrictions there are on the .NET provider. Is there any additional documentation besides the help file? Thanks for any help you can give. -- Murray ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Firebird-net-provider mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
