EO: Should I create primary keys?
EO: Should I create primary keys?
- Subject: EO: Should I create primary keys?
- From: Goodbye Bill <email@hidden>
- Date: Mon, 28 Jul 2003 05:46:10 -0400
HEEELP! SQL is pulling me back in! M-m-m-ust... n-n-not... go... back!
QUESTION:
Should I create assign/create my primary keys myself OR should I [is it
possible to] rely entirely upon EO to do it?
SCENARIO:
Wanting to be entirely object-driven, and not manipulate the database schema
directly, I have attempted to create all of my objects using ONLY EOModeler.
PROBLEM:
To create any relationship, one must specify the source and destination
properties (essentially, the primary and foreign keys within the table).
This means that the developer is forced to create the columns for the keys,
assign the key attribute, etc., both while creating the table and while
creating the relationship. This seems to violate the initial goal of EO,
which is to extrapolate the database and the object model.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.