In a message dated 2009.04.09 02:06 -0500, Ocke Janssen wrote:
In Base's Relationship pane... how is the cascade direction determined?
...
a typical concern is that if an Employee is deleted, the linked
EmployeePhoto record is deleted - but not the other way around: One
might need to delete or change an EmployeePhoto without deleting or
changing the Employee. So there is a clear unidirectional cascade.
How does Base determine that direction?
That depends on the database you use. As Base itself doesn't care, the
database has the responsibility to do the right.
But that's my question: Base does not seem to care about direction - but
that is the front end to the database. So how does the back end know what
we want?
... But in the relation ships design you can select what should happen on
each side differently. So in your example just define that when an
employee is deleted than his photo should be deleted as well and when
only his photo is deleted the employee stays untouched.
But, again, can Base offer any help in defining that relationship?
PS: The best list for Base questions is [email protected] or
[email protected]
Thanks! I had no idea about that.
John
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
