in reply to Class::DBI has_many
Now good database design, has taught me that when one has a 1:N relationship, one should construct a new table to hold that relationship.
I think you're over-normalizing here. This is a good idea for many-to-many relationships (there is no end to the half-baked ideas for doing that without a join table), but a join table on a one-to-many relationship is overkill.
----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer
: () { :|:& };:
Note: All code is untested, unless otherwise stated
|
|---|