On Fri, Feb 16, 2001 at 01:05:51PM -0500, Scott McCool wrote:
>
> My guess is that this is what was happening. I'm not sure of any
> way to confirm it though, how do I ensure that my select() is
> happening from a different database page then the insert?
Realistically, you can't. It's a guessin
ry 16, 2001 10:38 AM
To: [EMAIL PROTECTED]
Subject: Re: transactions -- whole table locked from reads too?
Scott,
did you try to do the insert and select on the same database page?
In BDB there is page level locking used, and the behavior you
describe sounds like that the insert has placed a
Scott,
did you try to do the insert and select on the same database page?
In BDB there is page level locking used, and the behavior you
describe sounds like that the insert has placed a page level lock
on the page where you try to do the select. Then it is correct behavior
of the database that y
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
