Re: Assertion failed - tried to dispose a non read-only transaction

Nick & Tobias,

I ran into this problem a couple weeks ago. Seems that data had been 
entered into a table multiple times somehow even though it had a primary 
key defined. I removed all the rows that didn't need to be there and 
that fixed it. This happened when I was messing around with the io page 
settings.

Tobias Downer wrote:

> Nick,
>
> I couldn't find this error in the debug.log you attached.  Does this 
> happen on a specific query, or series of queries before a commit?  Is 
> the problem reproducible?  If it is, can you send me the queries that 
> reproduce the problem.  Do you know if it happens when there is a 
> referential integrity constraint violation?
>
> Thanks,
> Toby.
>
> Nick wrote:
>
>> Hi,
>>
>> After an attempted commit, the following was dumped by Mckoi to the 
>> standard output:
>>
>> java.lang.RuntimeException: Assertion failed - tried to dispose a non 
>> read-only\par
>> transaction.\par
>>        at 
>> com.mckoi.database.Transaction.dispose(Transaction.java:2133)\par
>>        at 
>> com.mckoi.database.TableDataConglomerate.processCommit(TableDataCongl\par 
>>
>> omerate.java:3001)\par
>>        at 
>
>
>>
>> My entire transaction was lost - the equivalent of a rollback.  I've 
>> included a copy of the debug.log.
>>
>> Any pointers/ideas?
>>
>> TIA,
>> Nick
>
>
>
>
> ---------------------------------------------------------------
> Mckoi SQL Database mailing list  http://www.mckoi.com/database/
> To unsubscribe, send a message to [email protected]
>



---------------------------------------------------------------
Mckoi SQL Database mailing list  http://www.mckoi.com/database/
To unsubscribe, send a message to [email protected]