Hi all,
I know a lot of you use various means for PHP source control (CVS, SVN,
etc), which is all well and fine, but how do you manage source control
on your databases?
Say you've got an upgrade to a site, all of the new PHP files are
controlled by SVN, so you can rollback at any time, but
Richard Davey wrote:
Hi all,
I know a lot of you use various means for PHP source control (CVS, SVN,
etc), which is all well and fine, but how do you manage source control
on your databases?
Say you've got an upgrade to a site, all of the new PHP files are
controlled by SVN, so you can
Jochem Maas wrote:
lets forget that updating SQL schemas on massive DBs will likely take
so much time that you will have to plan in downtime on the systems involved ...
that's clearly out of the scope of this question.
Yes, this was part of the problem (and reason for my original post). At
Richard Davey wrote:
Hi all,
I know a lot of you use various means for PHP source control (CVS,
SVN, etc), which is all well and fine, but how do you manage source
control on your databases?
Say you've got an upgrade to a site, all of the new PHP files are
controlled by SVN, so you can
Richard Davey wrote:
Hi all,
I know a lot of you use various means for PHP source control (CVS,
SVN, etc), which is all well and fine, but how do you manage source
control on your databases?
Say you've got an upgrade to a site, all of the new PHP files are
controlled by SVN, so you can
I'm surprised (or rather, I'm unaware of) there is no native MySQL
solution for this situation.
Considering it's not a mysql specific problem I'd be surprised if there was.
Postgres lets you do database changes inside a transaction, eg:
begin;
alter table x add column y int;
...
commit;
On Wed, April 11, 2007 10:13 am, Richard Davey wrote:
I know a lot of you use various means for PHP source control (CVS,
SVN,
etc), which is all well and fine, but how do you manage source control
on your databases?
Say you've got an upgrade to a site, all of the new PHP files are
7 matches
Mail list logo
