Hello, On Oct 28, 2008, at 3:45 PM, Kieran Kelleher wrote:
Yeah ..... for single table logging apps. The *reason* EOF needs to generate and know about pks before saving is so that it can form the relationships before saving .... think to yourself how auto- increment could work in a multi-user environment where transactional saves are performed across many related tables, and you will understand that this "hassle" is a necessary thing ;-)
Well, not entirely. That's tricks like @@identity etc. are for, I understand.
Once on a customer's demand I've rewritten half of the EOF database level to support this for an EOF/Cocoa application; I am not sure it would be possible in WO/Java, but it might. Was a proper nightmare and heaps of legwork even in Objective C (where, if you happen not know the language, things generally go about thousand times easier than in the Java thing), but at the very end it worked pretty well, reliably and efficiently, and I have to admit there's something to the approach. For one, it makes a co-operation with non-EOF-based tools working on the same set of databases ways and ways easier and more robust...
Best, --- Ondra Čada OCSoftware: [EMAIL PROTECTED] http://www.ocs.cz private [EMAIL PROTECTED] http://www.ocs.cz/oc _______________________________________________ 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]
