I can't say I've had the issue you're describing, but I don't have much information to work with. Could you post more of those class definitions and the code involving the delete method? I'm sure that would help the other monks and I to analyze your problem.
Update: One of CDBI's badly-documented areas is using the has_many method. If you use two parameters, it assumes the field in the right-hand side of the relationship is the class name of the left-hand side. Thus:
If the field name in the RHS is different from the class name of the LHS, you need to use three parameters, the third defining the RHS field name.# concise class definitions FooBar->table('foobar'); FooBar->has_many(frobs => "Quux"); Quux->table('quux') #and a method on this FooBar instance... $wham->frobs #makes the (oversimplified SQL query) # SELECT * FROM quux WHERE FooBar = $wham
It appears you want to use this second form for your table structure. You did some of the time, but not others, so maybe it's just a mis-copy.FooBar->has_many(frobs => "Quux", 'foobar_id'); $wham->frobs # makes the (oversimplified SQL query) # SELECT * FROM quux WHERE foobar_id = $wham
In reply to Re: Class::DBI cascading delete problem?
by meredith
in thread Class::DBI cascading delete problem?
by zigdon
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |