Forgive me if I'm missing something obvious: I'm fairly new to all this.
I have three tables: Performance, Seat, Booking. Each booking has one seat, and one performance. So, I could add a couple of one-to-many relationships from Booking to the other two.
But, each seat+performance combination can only have one booking maximum (zero is allowed).
It seems to me that EO should be able to do something magical here to enforce that. In other languages I would just use code before allowing an insert to check that such a booking didn't already exist, but I have been conditioned by WO to expect it to perform miracles for me.
Anyone any ideas? Tom _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
