-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Database choices #27
Comments
I haven't really inspected the code, but what's the reason to generate .sql files? Why not use DBIx::Class::Schema->deploy? (Just sharing what I've used, not saying that it's better than any other solution). I haven't used ::Candy either, but I'm using deploy here if anybody wants an example. |
On Mon, Apr 14, 2014 at 08:33:00AM -0700, Björn Pettersson wrote:
Because deploy is a one-off deploy - great for development, sure. However the proposed tools are designed to handle versioning and upgrades too. The reason to generate .sql files is so (a) people can actually read the Plus, the diff files need something to diff against to generate them, and Basically, ->deploy was the original one that I wrote - and is still great (also, I assumed that Schema::Loader meant that you had people who really Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue http://shadowcat.co.uk/blog/matt-s-trout/ http://twitter.com/shadowcat_mst/ Email me now on mst (at) shadowcat.co.uk and let's chat about how our CPAN |
Wow, that was a patient answer! The more you know. Thank you. :) |
Given you're using DBIx::Class anyway, why not use DBIx::Class::Candy to declare the result classes, then DBIx::Class::Migration / DBIx::Class::DeploymentHandler to generate the .sql files?
SQLite would make a great choice for small blogs and for experimenting with the software, and PostgreSQL is going to be a vastly preferred 'real' deployment option to MySQL for lots of people.
Plus ::Candy is so much prettier :D
The text was updated successfully, but these errors were encountered: