Quick question, what directory is your application attempting to create
a database in//?
[EMAIL PROTECTED] wrote:
Greetings,
I've written a desktop application that uses Derby as its database,
and I've run into a problem. The app creates a database on first
startup. One client site is
a charm.
Cheers;
-- Matt Sanford
[EMAIL PROTECTED] wrote:
Hi, Hiram. You have hit on an issue that prevents multiple databases
from being run within the same VM. This is something we want to fix
in Derby, but it's a fairly big effort.
As it stands the only way to configure the Derby
of the maintenance portion of the
mission statement.
Just my €0.02
-- Matt Sanford
[EMAIL PROTECTED] wrote:
Hi Duminda,
I gues lots of ppl will appreaciate if you could develop a GUI for
Derby. Even programmers will apreaciate it. Why should the life of a
programmer be harder? We should promote
I just used Aqua Data Studio 3.7 with the following configuration :
Generic JDBC Driver, JDBC url of jdbc:derby:foo;create=true, Driver of
org.apache.derby.jdbc.EmbeddedDriver and Driver Location of
c:\path\to\db.
Aqua data studio was able to create and interact with the db just fine.
that goofed me up was the MY_TABLE is in all caps
even if not created that way. Unfortunately, this does not work in the
SQL-only ant environment you described.
Thanks;
-- Matt Sanford
[EMAIL PROTECTED] wrote:
Hi there,
Thank you guys for the advice.
I just wanted to prepare a file having those
your getByName. I do not know if this effects Windows the
same but it is worth a check.
Thanks;
-- Matt Sanford
[EMAIL PROTECTED] wrote:
Hi there,
I specified the host name by using the following code instead of
derby.properties.
NetworkServerControl server = new
NetworkServerControl
is that
internally Derby is using Integer.valueOf which does not recognize as
a valid number.
Thanks;
-- Matt Sanford
[EMAIL PROTECTED] wrote:
Hi, I'm wondering if someone has run into this and can
help me understand what's happening.
I'm porting some JDBC code from Another Database to Derby;
I'm using
with the transaction log flushing under heavy write load ?
I could find almost no reports of these errors when searching.
Thanks;
-- Matt Sanford
[1] RedHat AS 2.1 with 4 CPUs and 4GB RAM. Using ext3 file systems.
Java Version : Sun j2sdk1.4.2_03, using options : -server -Xms1600M
-Xmx1600M -XX:+AggressiveHeap