I use to create the SQL queries by hand because if they are complicated they can be done much better in the DB directly.
I don't use a versioning system because exactly when I wanted to try DBIx::Class::Schema::Versioned I wanted to do it for an Oracle database but I read that this module doesn't support Oracle. Octavian ----- Original Message ----- From: "Matija Grabnar" <mat...@serverflow.com> To: <catalyst@lists.scsys.co.uk> Sent: Friday, July 16, 2010 9:01 PM Subject: [Catalyst] Best practice for setting up database in a complexproject? >I was wondering what the experienced Catalyst developers use to set up a > database in a project. > Do you write the database definition mysql/postgresql format, and then > dump schema to get the Perl classes, or do you write Perl class > definitions and use something else to output the table creation > statements for the > database of your choice? > > And what do you do when the structure of the database changes (new > tables, new columns, new indexes or foreign keys) - do you use a DB > versioning thing, or do you do it by hand? If you do use a DB versioning > tool, > which do you recommend? > > _______________________________________________ > List: Catalyst@lists.scsys.co.uk > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ > Dev site: http://dev.catalyst.perl.org/ _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/