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 your select has to wait until the commit which
releases the locks placed by the insert.
A possible solution would be to use 'dirty read', i.e., non-locking
read in select, but I do not know if BDB provides such.
My own Innobase table handler allows you to read and insert data
concurrently with no interference from locks, because Innobase
does in a select a consistent non-locking read, in the style of Oracle.
But MySQL/Innobase is not available yet, it will come out in
MySQL 3.23.3x in a few days (see my posting a couple of hours ago).
Regards,
Heikki Tuuri
Innobase Oy
Helsinki, Finland
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
