Hello Tim,
 Can you add the "Primary Key" value/information on configuration.serversessionlocks ?
 IOW, I want to know which record is edited and prevent someone else to edit it fast.

Thank you

Michael,

<< Can you add the "Primary Key" value/information on configuration.serversessionlocks ? >>

Hmm, that is going to be a problem.  To get that information, EDB will have to perform I/O to cross-reference the row numbers back to the primary keys, and I'm not really happy about that information query causing general I/O on the underlying tables.  With a lot of sessions/locks, simply querying that table could end up being a hotspot.

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<< Hmm, that is going to be a problem.  To get that information, EDB will have to perform I/O to cross-reference the row numbers back to the primary keys, and I'm not really happy about that information query causing general I/O on the underlying tables.  With a lot of sessions/locks, simply querying that table could end up being a hotspot. >>

Well i you can do it "optional" like FileBuffers.
In this case the EDB Server is used with 5 users and around 4 database so the overhead will be small.

I really need an instant way to check if a record is locked when i use EDB Server.

I'm thinking changing the "RecordLockRetryCount" to 1 and "RecordLockWaitTime" to  0
but is this dangerous ? Also i have to use "try...except" to eat up the expection and show my
own dialog which i do not prefer ...

Any suggestions other suggestion then ?

Thank you