in reply to Class::DBI and DB design
apologies if I'm way off base here,
Update: Yup, way off base.. nothing to see here people.. move along..
If I read the Class::DBI docs right, I need to add a "relation_id" column to the user_capabilities table, even if I'm never going to need it. Why? What was the reasoning behind that restriction?
I don't think you do have to. You just want to make 'uid' the primary key for the table. Are you after something like this maybe?
package My::Class::DBI::User; use base 'Class::DBI'; __PACKAGE__->table('user'); __PACKAGE__->columns( All => qw/ uid name login / ); __PACKAGE__->has_many('logins', My::Class::DBI::UserLogin => 'uid'); package My::Class::DBI::UserLogin; use base 'Class::DBI'; __PACKAGE__->table('user_login'); __PACKAGE__->columns( All => qw/ uid timestamp / ); 1;
cheers,
J
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: Class::DBI and DB design
by v_thunder (Scribe) on Jun 06, 2003 at 17:32 UTC | |
by edoc (Chaplain) on Jun 06, 2003 at 17:46 UTC |