one to one relationship revisited (has_own)

[prev] [thread] [next] [Date index for 2005/01/20]

How long winded should i be?? ... I'll start with not very.

i think it would be cool if programs could distinguish if has_a relationships
were one to one or many to one. AsForm treats them as many to one by making a
select box of all existing foreign objects. 

So, I'm thinking of making a "has_own" relationship. I think it will be real
short.

package Class::DBI::Relationship::has_own;
use base qw/Class::DBI::Relationship::has_own;
1;

No internal differences i can think of but different name so systems will know
this is a true one to one. So for example:
Person->has_own(phone => "Phone");

 Then AsForm could instead of making a select box of all phones, make input
box(s) for column(s) in phone. 

Furthermore, i thought that create and update may be able to automatically
create and update phone:

$prsn = Person->create( {...., phone_id => {...} } );
$prsn->upd .. . Well update wouldn't need to do anything different.
Delete however would cascade like has_many. 


thanks and I look forward to hearing "See this thread
http://wetalkedaboutthisyoulazyidiot"/



=====
pjs

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com