![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 11 to 12 of 12 total |
![]() |
Tue, Jul 30 2013 10:39 AM | Permanent Link |
Barry | >>Yes, it's the long-running query in your application that is blocking the
other query from being able to get the snapshot of the locks for your application's session.<< That's too bad because it certainly limits the usefulness of accessing ServerSessionLocks table to see if anyone has a table open. I will go back to trying an exclusive lock on the tables instead. Barry |
Wed, Jul 31 2013 1:25 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Barry,
<< That's too bad because it certainly limits the usefulness of accessing ServerSessionLocks table to see if anyone has a table open. I will go back to trying an exclusive lock on the tables instead. >> Yeah, it's something that I'm hoping I can address at some point. The lock information is very low-level stuff, and unfortunately there aren't any lockable objects at that level because they are assumed to be per-session. So, the only way to synchronize access at this point is through a lock on the session itself. Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |