Leandro Hermida wrote:
I've done some troubleshooting, dumping out the schema object, and found
that cascade_copy => 1 and cascade_delete => 1 are set at every
relationship in question, so it seems that something is being missed by
SQLT?
On Wed, May 25, 2011 at 3:22 PM, Leandro Hermida
<[email protected] <mailto:[email protected]>> wrote:
Hi everyone,
I feel like I'm just not seeing something, in a DBIx::Class schema I
have when I run deployment_statements all my constraints have ON
DELETE CASCADE and/or ON UPDATE CASCADE except for one and I can't
understand why it has nothing when all the rest do since it is
defined exactly the same way as others. I have written standard
DBIx::Class result class files and I don't set anything explicitly
for on delete or on update at all, so everything default in that regard.
Would anyone know why one single constraint in a schema would not
have no ON DELETE and/or ON UPDATE when all the others do?
regards,
Leandro
Sorry for attending to this so late - did your issue ever get solved?
_______________________________________________
List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/
Searchable Archive: http://www.grokbase.com/group/[email protected]
