Re: issue with AutoInc field and locks
- From: "Koen" <koen@xxxxxxxx>
- Date: Wed, 23 Apr 2008 13:39:34 +0200
In Delphi a TGUID is a longword.. in access: a Number / Longint?
"Koen" <koen@xxxxxxxx> wrote in message
news:480f1e24@xxxxxxxxxxxxxxxxxxxxxxxxx
How to declare the field in the database when using a GUID?
"Vitali Kalinin" <vitkalinin@xxxxxxxxx> wrote in message
news:47a04ba4@xxxxxxxxxxxxxxxxxxxxxxxxx
1.. If it is possible try to avoid sequence autoinc in new developments,
since if some day you will decide to go 3 tiers disconnected mode it
would be general PITA. Use GUIDs instead, since they could be easily
generated on a client side
2.. I think that you can achieve exactly same effect if you will assign
Conection IsolationLevel to ilRepeatableRead and do select inside
transaction. But I should warn you that such design, i.e. usage of server
side cursors very badly affects performance in multi user environment.
Could you please elaborate what you are actually trying to achieve?
Definitely there should be better way.
.
- Follow-Ups:
- Re: issue with AutoInc field and locks
- From: Bill Todd [TeamB]
- Re: issue with AutoInc field and locks
- References:
- Re: issue with AutoInc field and locks
- From: Koen
- Re: issue with AutoInc field and locks
- Prev by Date: Re: issue with AutoInc field and locks
- Next by Date: Re: Use GUID instead of AutoInc
- Previous by thread: Re: issue with AutoInc field and locks
- Next by thread: Re: issue with AutoInc field and locks
- Index(es):
Relevant Pages
|