in reply to Class::DBI and - possibly - complex data structures
Your PersonName class has a bug:
PersonName->columns( All => qw(person firstname name) );Since you don't have a 'name' field defined, that should be 'lastname'.
Why does each person have more than one name, though? If it's the case that one person can be "John Smith" and "Jane Doe", it's appropriate to have names in a separate table. If, however, you mean that one person has a first and a last name, then you probably want to move those into your person table. If that's the case, you can collapse this down to one table.
package Person; use strict; use warnings; use base 'My::DBI'; __PACKAGE__->table( 'person' ); __PACKAGE__->columns( All => qw(person_id sex modified first_name last +_name) );
If, however, a person can really have more than one name (aliases), then two tables can suffice.
package Person; use strict; use warnings; use base 'My::DBI'; Person->table( 'person' ); Person->columns( All => qw(person_id sex modified) ); Person->has_many( names => 'PersonName' ); package PersonName; use strict; use warnings; use base 'My::DBI'; PersonName->table( 'person_name' ); PersonName->columns( All => qw(person_name_id person_id first_name las +t_name) );
And in your actual code:
my $person = Person->retrieve( $person_id ); while ( my $name = $person->names ) { printf "%s, %s\n", $name->last_name, $name->first_name; }
It also looks like you could use a brush-up on database design. Microsoft has a decent article on Database normalization basics. It's fairly concise and easy to understand -- as much as the topic is easy to understand, that is.
Cheers,
Ovid
New address of my CGI Course.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: Class::DBI and - possibly - complex data structures
by Evil Attraction (Novice) on Sep 06, 2003 at 00:06 UTC |