On 2013-08-26 23:25, Paul J Stevens wrote:
On 08/26/2013 03:38 PM, Thomas Raschbacher wrote:
on another note: wouldn't it be good to have these migrations
TRANSACTION based? (maybe even with a stored procedure?)
Of course full atomicity would be better. Also quite difficult to
achieve in this case. I have no idea what you're suggesting with regard
to stored procedures. I don't think migrating in this context could be
done in the database - unless you want to rewrite non-trivial parts of
the message handling code in some embedded language.
I know what you mean about atomic DB stuff in code .. can be quite a
pain.
I am not entirely sure what is done during the migration, so can'T judge
about doing it in an SP ^^
I do have some experience with Stored Procedures, so if you needed
something specific (Postgres mostly) I can probably help. I had to write
a lot of Stored Procedured (for MS SQL though) in one of my previous
jobs (some of them were ridiculously long because they had grown which
is also a pain of course).
That said I'm sure there is a good place for stored procedures. They
can
enhance performance in several places I'm sure. I just don't have to
time or inclination to pursue that path myself.
Maybe I'll have a look at some SQL in DBMail myself to see what could be
done ;)
Finally, I've added automatic schema migrations to the master branch,
but neither MySQL nor SQLite are very good at atomic schema migrations.
can'T comment on that since i switched to Postgres for all my DB needs
quite a few years ago (before MySQL had stored procedures,.. ;))
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail