On 02.09.11 07:40, Trejkaz wrote:
Hi all.
We have tests (and apps, naturally) which start up the network server
and then test that connecting to it works. One test runs our wrapping
around the server and uses bare JDBC code to verify that it's
connectable. The other test runs our wrapping
On Fri, Sep 2, 2011 at 4:18 PM, Kristian Waagan
kristian.waa...@oracle.com wrote:
On 02.09.11 07:40, Trejkaz wrote:
Hi all.
We have tests (and apps, naturally) which start up the network server
and then test that connecting to it works. One test runs our wrapping
around the server and uses
Hi all.
I am getting an error like this when the database directory has a
semicolon in it:
java.sql.SQLException: The URL
'jdbc:derby:C:\Users\Me\Desktop\one;two' is not properly formed.
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:98)
Hi
My application (Anthillpro) is currently Apache Derby - 10.1.3.1. I am looking
at various ways to improve performance.
I would like to try setting the following property and am looking for some
assurance from experienced users that there will be no ill affect.
Any comments would be much
Increasing the pageCacheSize will of course increase the heap memory used by
your running application. If you have the memory to spare, I'm not aware of
any harm to increasing it.
As for performance and if increasing it would help; it would most likely be
determined by how you are using the
Hi folks,
we are always working to make Derby more secure; in this day and age,
security is ever more on people's minds for obvious reasons;
IT systems are everywhere and the bad guys never tire of finding new
holes to break them. Up till now, Derby creates database files and logs
using the
Thanks David
From: David Zanter [mailto:dzan...@gmail.com]
Sent: Friday, September 02, 2011 01:31 PM
To: Derby Discussion derby-user@db.apache.org
Subject: Re:
Increasing the pageCacheSize will of course increase the heap memory used by
your running application. If you have the memory to
+1 for more restrictive permissions. Actually when I run Derby on Unix
it runs under own user+group and database files are not accessible by
others.
On Fri, Sep 2, 2011 at 7:31 PM, Dag H. Wanvik dag.wan...@oracle.com wrote:
Hi folks,
we are always working to make Derby more secure; in this day
Unless it is completely unavoidable, it should be possible to install a later
version AND NOT BREAK AN EXISTING APPLICATION. To do so is rude and can be
very disruptive.
- Original Message -
From: Dag H. Wanvik dag.wan...@oracle.com
To: Derby Discussion derby-user@db.apache.org
