db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glenn Marintes <gl...@janet.co.jp>
Subject Re: derby and torque transaction handling
Date Thu, 06 Apr 2006 12:09:35 GMT
Andreas Korneliussen wrote:
> Glenn Marintes wrote:
>> Hi Dan!
>> Thanks for your quick reply.
>>> Derby supports multiple connections. Other than that I'm not sure I can
>>> help. Does this tutorial help?
>>>   
>> I will verify Derby's multiple concurrent connections support then. I 
>> had got some info from one
>> of my superiors telling me that Derby does not support multiple 
>> concurrent Connections :(
>> Its best to try it out I think.
>>
>>> http://db.apache.org/derby/integrate/db_torque.html
>>>   
>> Yes. I had read this tutorial.
>>
>> Regarding Derby, I'm having some trouble with it.
>> I get an SQLException with "XSDF1" sql state when I try to 
>> executeQuery("CREATE TABLE <more ...>");
>>
>> Its kinda weird because the same executeQuery call works on another 
>> test class. But when I run
>> the real app, I always get the XSDF1 exception. Please note that I 
>> have tried the execute() and executeUpdate()
>> too.
>
> You should use execute() or executeUpdate(..) when executing "CREATE 
> TABLE.."
>
>>
>> I have 1GB+ free space on the drive where Derby db is being created :(
>> What are the other reasons for the XSDF1 sql state?
>>
>
> Other reasons may be that the file exists already. If you have the 
> stack trace for the exception, we could check the source to see where 
> it was thrown from.
>
> Andreas
>
>> Thanks and more power!
>>
>
>
Also, please note that I have verified the file  
E:\docs\old\workspace\workspace_jb\JavaBackupCl\work_dir1\db\seg0\c450.dat
does not exist before and after the XSDF1 exception

-- 
*******************************************
*
* Glenn M. Marintes
* Software Development Section
* JANET
* 


Mime
View raw message