problem with BDB table, error -30996

2002-02-22 Thread Geoffrey Soh
Hi, Has anyone got the following error on a BDB table : read_const: Got error -30996 when reading table We did some load testing on a particular BDB table and got this when we tried to run 20 concurrent queries on the table. The query in question works fine when the database in

Re: BDB table error

2001-09-18 Thread Michael Widenius
Hi! > "Dana" == Dana Powers <[EMAIL PROTECTED]> writes: Dana> Thanks for the reply! I can understand the situation with muti statement Dana> transactions, but I'm not using transactions ( at least from my Dana> perspective ); Im only issuing single 'atomic' statements. It would make Dana> m

Re: BDB table error

2001-09-17 Thread Dana Powers
and that seems so cumbersome given that the solution is the same in every case. dpk - Original Message - From: "Michael Widenius" <[EMAIL PROTECTED]> To: "Dana Powers" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: M

Re: BDB table error

2001-09-17 Thread Michael Widenius
Hi! > "Dana" == Dana Powers <[EMAIL PROTECTED]> writes: Dana> Certainly I understand how the deadlock can occur, but the question is why Dana> is this acceptable behaviour? Is the application developer expected to Dana> handle this case? If so, how? and shouldnt this be included in the manu

Re: BDB table error

2001-09-16 Thread Dana Powers
t; <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, September 16, 2001 2:14 AM Subject: Re: BDB table error > Dana, > > if you have page level locking, you can easily > get a deadlock from an atomic insert done as > a single tran

Re: BDB table error

2001-09-16 Thread Heikki Tuuri
Dana, if you have page level locking, you can easily get a deadlock from an atomic insert done as a single transaction, and another user doing an atomic select in another single transaction. It happens this way: User A User B insert recordselect record from second

AW: BDB table error

2001-09-15 Thread Christian Sage
, of course, whether this is workable. And, yes, from a design point of view it IS ugly. cs > -Ursprüngliche Nachricht- > Von: Dana Powers [mailto:[EMAIL PROTECTED]] > Gesendet: Sonntag, 16. September 2001 00:14 > An: Christian Sage > Cc: [EMAIL PROTECTED]; [EMAIL PROTEC

Re: BDB table error

2001-09-15 Thread Dana Powers
ot; <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, September 15, 2001 3:08 PM Subject: AW: BDB table error Dana, a deadlock can easily occur on a single table with row-level (or page-level) locking. What happens is something like the following: connectionhas lock on

AW: BDB table error

2001-09-15 Thread Christian Sage
ffense intended, as I say, I may be totally off the beam here. Cheers, Christian Sage > -Ursprüngliche Nachricht- > Von: Dana Powers [mailto:[EMAIL PROTECTED]] > Gesendet: Samstag, 15. September 2001 23:37 > An: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Betreff: Re: BDB

Re: BDB table error

2001-09-15 Thread Dana Powers
es. dpk - Original Message - From: "Dana Powers" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, September 15, 2001 1:52 PM Subject: BDB table error > Im getting this error from attempted inserts into a BDB table using > my

BDB table error

2001-09-15 Thread Dana Powers
Im getting this error from attempted inserts into a BDB table using mysql-3.23.42 ( same error but more often in 3.23.38 ): Could not insert new row into SESSION_DATA: Got error -30996 from table handler First - I have not been able to find what this error means in either the source code, online