Re: Tracking and deploying changes in (MySql/Maria) DB schema ...

We have a home-rolled, replay from the start, SQL delta management system at work that’s actually pretty good, if slow, so I have no experience with this—DBIx::Class::Schema::Versioned—but I always wanted to try it.

Comment on Re: Tracking and deploying changes in (MySql/Maria) DB schema ...

Replies are listed 'Best First'.
Re^2: Tracking and deploying changes in (MySql/Maria) DB schema ... by LanX (Saint) on May 22, 2019 at 19:36 UTC
Well dbix-class would require changing the code base. Home rolling sounds like the second best solution. (I'd probably also try playing around with triggers on our dev server) Probably the easiest way is political: I send an email always requiring explicit ALTER TABLE code for each change and prepare playing the finger pointing game if something crashes. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}	[reply]

Replies are listed 'Best First'.

Re^2: Tracking and deploying changes in (MySql/Maria) DB schema ...
by LanX (Saint) on May 22, 2019 at 19:36 UTC

Home rolling sounds like the second best solution. (I'd probably also try playing around with triggers on our dev server)

Probably the easiest way is political:

I send an email always requiring explicit ALTER TABLE code for each change and prepare playing the finger pointing game if something crashes.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

[reply]