Well.. I finally got it working the way that I wanted. And yes - a column may appear in more than 1 page.
Here is the way I have designed it.
|
|
|
|||||||||||||||||||||||||||||||||
Two things I noticed which Class::DBI required -
1) In table page_column, "column" should be the primary key and not "page"
2) while coding the relationships, its better to use "page" and "column" column names instead of "page_id" and "column_id"
Now the "mapping" stuff as suggested by PodMaster works like a charm, and I can get all columns in page easily.
Thankx a lot for all the help.
I know that this design may not be realistic but it
very much suffices me for now.
--
arc_of_descent
In reply to Re: Class::DBI has_many
by arc_of_descent
in thread Class::DBI has_many
by arc_of_descent
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |