Hello Raphael, couldn't resist answering your question. I am a married man, and
I sure look forward to have a 1:1 relation between clearly differentiated
"objects" (i.e. persons) :)
Best regards everyone,
Álvaro Coronel.
Raphael Mankin <[EMAIL PROTECTED]> wrote:
Make the FK a unique attribut
Hi,
there are several reasons why one may want a 1:1 relation
- the data belongs to logical different entities. Maybe later one wants to
release te 1:1 relation
- part of the data in a table is expensive to read but is not always
needed. Torque always reads the whole column.
Thomas
Make the FK a unique attribute, then there can be only one 'child' of a given
parent.
But why do you want a 1:1 at all? Surely if two objects are 1:1 then they are
two parts of the same object -- unless one part is optional.
On 01-Jul-2005 Thomas Fischer wrote:
>
>
>
>
> Hi,
>
> 1:1 and n
Hi,
1:1 and n:m relations are not supported out of the box by Torque, as far as
I know.
However, as a 1:1 relation is a special case of a 1:n relation, there
should be no real problems there. Only thing you have to do is verify that
one object is referenced only by one other object. You can e
