Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Users List" <torque-user@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
In-Reply-To: <OF92A0CCA0.CC2BB666-ONC1256FAC.004F20F5@LocalDomain>
Subject: RE: Torque apache derby embedded support
To: "Neal" <syph4@ecis.co.za>
Cc: "Apache Torque Users List" <torque-user@db.apache.org>
Message-ID: 
 <OF033E662B.A70D48B7-ONC1256FAC.00500873-C1256FAC.00508B5F@seitenbau.net>
From: Thomas Fischer <fischer@seitenbau.net>
Date: Fri, 18 Feb 2005 15:39:44 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII


Hi,

due to a bug in the derby jdbc driver, Torque does currently NOT work with
derby, neither embedded nor via network. See the mail I posted to the users
list about a week ago. You might be able to read from the database, but
writing does not work.

Your configuration seems ok to me, though I am not sure if you can omit the
host definition. The driver should be ok.

       Thomas


"Neal" <syph4@ecis.co.za> schrieb am 18.02.2005 15:16:51:

> Hi,
>
>
>
> I have noticed that support for Apache Derby has been added in CVS but
not
> in the stable release.
>
>
>
> Does anyone have Torque running with derby as an embedded database?
>
>
>
> Which driver should be used to do so?
>
>
>
> I would appreciate some input on the structure of the config file:
>
>
>
>   torque.database = derby
>
>   torque.database.createUrl = jdbc:derby:test
>
>   torque.database.buildUrl = jdbc:derby:test
>
>   torque.database.url = jdbc:derby:test
>
>   torque.database.driver = org.apache.derby.jdbc.EmbeddedDriver
>
>   torque.database.user = user
>
>   torque.database.password = user
>
>   #torque.database.host = 127.0.0.1
>
>   #torque.schema.dir = ./schema
>
>
>
> Kind Regards,
>
> Neal
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org