Comments on: How do your DBIC result base classes look like?

By: Moritz Onken

Moritz Onken — Fri, 22 May 2009 17:42:18 +0000

Thanks for your thoughts on this.

The reason why I drop those constraints is that I had some problems when I tried to populate my database (e.g. with a dump). PostgreSQL complained on a regular basis that some foreign key constraints are violated. So I thought dropping them altogether would save me from that problem.

Anyway, I think it wasn’t the best idea and there is probably a different way to work around this.

By: Moritz Onken

Moritz Onken — Fri, 22 May 2009 17:35:31 +0000

I thought DBIC would try to load that class. Did not try it yet :-)

By: fREW Schmidt

fREW Schmidt — Fri, 22 May 2009 02:01:29 +0000

Why do you do MySchema::Base::Result instead of just MySchema::Result?

By: Pedro Melo

Pedro Melo — Thu, 21 May 2009 20:08:15 +0000

Hi,

my base class for Result’s starts simply as

package Base;

use strict;
use warnings;
use base ‘DBIx::Class’;

__PACKAGE__->load_components(qw(InflateColumn::DateTime Core));

I don’t know why your DBIC is asking you to declare a table, or even columns, that does not make any sense to me.

I have others, more complex, including one that keeps track of all changes to the table.

Best regards,

By: Matt S Trout

Matt S Trout — Thu, 21 May 2009 12:10:50 +0000

You’re insane. DBIx::Class does *not* “handle foreign keys anyway”, it’s designed to do things correctly on an actual database and only incidentally, probably, work on sqlite or MyISAM.

Throwing away your foreign keys like that is intensely scary – it’s like going through every line of perl on your system deleting ‘use strict’ and ‘use warnings’ and at least as dangerous.

And as for “Since I’m a little bit paranoid about collision I set the check parameter so the component checks before inserting a new row if a column with that id is already there” – if you actually care, call ->add_unique_constraint to constrain it on the database side.

Constraints are good. use them.

– mst