Keep in mind that when Class::DBI's built in relationships fail you, you can always add a method to it that runs an arbitrary SQL query and returns one or more objects. That might be the best thing to do in your case. There will always be things that an O/R mapping tool doesn't handle well, and that's when the ability to add hand-coded SQL transparently becomes important.
In reply to Re: Class::DBI and DB design
by perrin
in thread Class::DBI and DB design
by v_thunder
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |