If I start a transaction (set autocommit=0 in the command line utility),
then do an "insert...." in one session, then open a second session and try
to do a select on that table, before the first session has committed, the
select just hangs. Once I commit in the first session, my select proceeds
fine.
Is there some reason the whole table seems to be locked from reads just
because someone has an uncommitted transaction?
The table type is BDB, it's running on Solaris 7/SPARC.
Thanks for any help you can offer!
-Scott
---------------------------------
Scott McCool
[EMAIL PROTECTED]
(703)847-3303x2051
---------------------------------
