Chuck Hill wrote:
Hi,
On Feb 9, 2006, at 8:04 PM, Kieran Kelleher wrote:
One thing about EOModeler is that every attribute has optimistic
locking turned on by default. This creates big WHERE clauses which
can slow you down on non-indexed fields. My feeling is that
optimistic locking should be turned on on essential fields only and
then index those since WO _will_ use then in sql WHERE clauses.
I've heard this a number of times, but doubt that it is true. The
WHERE clause also includes the primary key. It seems to me that any
query optimizer worth its name should be able to grab that one row and
very quickly evaluate the rest of the WHERE conditions on it.
Chuck
Mike Schrag recently tested this and it does make a difference. How
important that is is up to the individual. See Mike's email 'Managing
EOF Caching'. I forget which database he was testing and I meant to do
something similar for Postgres to see if smarter/dumber databases made
any difference.
-arturo
_______________________________________________
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]
