Re: What's is better solution for Lock? Use Timestamp or "mark all fields"
Re: What's is better solution for Lock? Use Timestamp or "mark all fields"
- Subject: Re: What's is better solution for Lock? Use Timestamp or "mark all fields"
- From: Arturo Perez <email@hidden>
- Date: Tue, 01 Nov 2005 16:29:25 -0500
Chuck Hill wrote:
On Nov 1, 2005, at 10:30 AM, Luis Miguel Espinoza wrote:
1. Is faster for EO use one Column as lock or faster use all fields
that I consider to need for lock,? Can it make slower or faster my
application or if I use anyone my applicaction benchmark will be equal??
Compared to everything else that runs as part of your application, it
won't make any difference what you lock on (well, other than large
BLOB/CLOB fields). As long as the PK is used for locking (and you can
NOT avoid this!), the cost will be for the database to make some field
value comparisons on a single row. This will be very fast and not
something I'd even bother to think about.
The important thing, and just about the only thing that makes a
difference, is to ensure that you don't lock on a column that requires a
byte-to-byte comparison. These would include BLOB, CLOB, other LOBs and
large text fields (like a varchar(1024)), maybe even things like NUMERIC
columns.
-arturo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden