Subject | RE: [firebird-support] Distributing/deploying Stored Procedures |
---|---|
Author | Louis van Alphen |
Post date | 2015-03-13T09:14:41Z |
Such a function is a disaster waiting to happen. No tool can recreate any
data transformations / data refactoring that is usually part of a release.
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com]
Sent: 13 March 2015 11:06 AM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Distributing/deploying Stored Procedures
On 13/03/2015 00:37, 'Andrew Zenz' andrew@...
<mailto:andrew@...> [firebird-support] wrote:
Or must I ship ISQL.exe with my application and INPUT scripts?
Even if you do that the dependency issues will be a right pain, it'll be a
lot of hard manual work to put the scripts together and test them.
What's missing from most (all?) database engines is a version control system
integration and a single command which says "update all the various bits of
this database to match what's changed in the version control system" without
the user having to worry about the dependencies, which really are a database
internal gubbins issue that the database should look after.
--
Tim Ward
[Non-text portions of this message have been removed]
data transformations / data refactoring that is usually part of a release.
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com]
Sent: 13 March 2015 11:06 AM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Distributing/deploying Stored Procedures
On 13/03/2015 00:37, 'Andrew Zenz' andrew@...
<mailto:andrew@...> [firebird-support] wrote:
Or must I ship ISQL.exe with my application and INPUT scripts?
Even if you do that the dependency issues will be a right pain, it'll be a
lot of hard manual work to put the scripts together and test them.
What's missing from most (all?) database engines is a version control system
integration and a single command which says "update all the various bits of
this database to match what's changed in the version control system" without
the user having to worry about the dependencies, which really are a database
internal gubbins issue that the database should look after.
--
Tim Ward
[Non-text portions of this message have been removed]