db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean T. Anderson" <...@bristowhill.com>
Subject Re: JDBC Driver returns read-only column metadata
Date Fri, 07 Oct 2005 15:45:28 GMT
Satheesh Bandaram wrote:
> Could you post the exact error message and execution stack? It would be
> even more benificial if you could create a test case that shows the
> problem, without using Torque.
> I am willing to help, but haven't used Torque before...
> Satheesh

This problem was previously logged as DERBY-142 by a Torque developer, 
who included a test case. Here's an extract from what Thomas posted to 
torque-dev@db.apache.org ( for reference, 

) :

> By the way, last time I tried it, Torque did not work with Derby and the
> network driver. The problem was that the network driver in the meta-info
> declared all columns to be read-only, which causes a library used
> internally in Torque (village) to refuse to write any datasets into the
> table. The problem is described in the Bug DERBY-142 in Derby's Jira.
> However, in future releases of Torque, it is quite probable that village is
> removed, so this will not be problematic any longer.


> Davor Prezel wrote:
>>I'm trying to get Derby 10.1 Net Server to work with Torque, but when
>>I try to insert or update the ColumnMetadata returns the read-only
>>flag as true nad therefore Torque cannot save it.
>>I have checked and the databse itself is NOT readonly. I have not used
>>any extra parameters to get the Derby to start, nor did I put some
>>extra parameters to Derby JDBC client.
>>I'm using Derby JDBC client bundled with the Derby Server 10.1
>>I appreciate the help on this. Thanks

View raw message