Am 19.06.2013 15:32, schrieb Paul J Stevens: > On 06/19/2013 10:37 AM, Harald Leithner wrote: >> Maybe a better sql change communication would be great, > > I agree. A controlled change mechanism would be really nice to have. I > don't see an elegant way to provide it however. > > One option I've looked at is sqlalchemy-migrate, but that would require > trusting schema management and only schema management to sqlalchemy, > which seems a bit overkill to do
hmm - not really our internal cms (written in PHP) has for any module a sql-scheme in an array (field, name, type, lenght, unsigned 0/1) and calling "create.php" as loggd in user is since the beginning there to apply any changes like new fields and keys depending on the current active modules and options for dbmail this should be in fact easier because there are no conditions which fields, views and keys the db-scheme needs to have, if i would be a c-programmer i could step in here but sadly i'm not :-(
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
