nicinch <[email protected]> writes: > > Has anybody had this behaviour and a way to fix?
Try to open the database in ij and see it it is read-only at the Derby level. If you can make modifications using ij, the error lies outside Derby. e.g. something like $ java -jar <DERBYROOT>/derbyrun.jar ij > connect 'jdbc:derby:<mydb>'; > create table foo(i int); > drop table foo; > exit; Thanks, Dag > > Thanks for your help.
