I don't want the database to be unsafe by default, but an
option to run it in "non fail safe" mode. And this mode should
be possible to enable without recompiling.
Steen
> I think it is wrong to make non safe database the default, but am
> interested in hearing the communities opinion. I do rea
I always serialize the object to a byte[] and then use setBinaryStream(),
e.g.
byte[] b = ... // serialize arbitrary object to byte[]
ByteArrayInputStream ins = new ByteArrayInputStream(b);
ps.setBinaryStream(psParamIndex, ins, b.length);
I've found this to be reliable. FYI Problems with us
hi,
Derby seems to support JDBC 3.0 Connection.getGeneratedKeys()
(http://incubator.apache.org/derby/manuals/reference/sqlj229.html), but
using the Universal Driver,
connection.getMetaData().supportsGetGeneratedKeys() returns false. Does
the universal driver for derby not support getGeneratedKe
Mike Matrigali wrote:
Steen Jansdal wrote:
Daniel John Debrunner wrote:
If you build Derby yourself you can test out a faster version of Derby
that has relaxed durability.
By relaxed durability I mean that:
- a commit no longer guarantees that the transaction's modifications
will survive a
How about you first serialize your object into a
byte[] and then do a setBytes() ? And then to read it
back you can do getBytes() and then deserialize from
that byte[]. Would that work?
Regards,
Ali
--- Mithun Ruikar <[EMAIL PROTECTED]> wrote:
> Hello there ,
>
> I have problem while setting
Hello there ,
I have problem while setting Blob value to table created in derby.
I had created : a datasource by parameter create=true.
and then created new table in it with one column with Datatype as Blob.
But when I tried to setObject value to this column ( by serializable object awt.color)
Drone is a Java IRC bot written with the RIFE framework. It has a
modular API that makes it possible to easily extend and customize the
active feature set.
It sports a modern web administration interface to handle all common
tasks and a public logging section with an advanced web search. It als
I think it is wrong to make non safe database the default, but am
interested in hearing the communities opinion. I do realize other
database systems do pick this as their default.
I suggest that if it is decided to
"support" this mode that the logging system be changed to somehow
record that the
I initially did design it such that new tables were created instead of new
databases. For various reasons, I decided to refactor the design and go with the
new databases strategy.
Having now experienced this issue, I'll probably just revert back to the initial
design. The 'skeleton database file s
Daniel John Debrunner wrote:
If you build Derby yourself you can test out a faster version of Derby
that has relaxed durability.
By relaxed durability I mean that:
- a commit no longer guarantees that the transaction's modifications
will survive a system crash or JVM termination.
- the database
10 matches
Mail list logo
