db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alvaro Coronel <alvarocorone...@yahoo.com>
Subject Re: jdbc task put username instead of db name in schema file
Date Tue, 27 Jan 2009 18:52:51 GMT
The on etime I installed Oracle DB, I found it most confusing regarding "user" and "schema".

Suffice to say that in Oracle it would make sense to use the username as the schema name.

My 1/2 cent :)

Álvaro




________________________________
From: Thomas Fischer <fischer@seitenbau.net>
To: Apache Torque Users List <torque-user@db.apache.org>
Sent: Tuesday, January 27, 2009 10:05:13 AM
Subject: Re: jdbc task put username instead of db name in schema file

> hmmmm, but then why make the torque user able to specify the
> 
> torque.database.name
> 
> property in build.properties ?

correct, I overlooked that back then. Please create a jira issue.

     Thomas
> 
> Thomas Fischer ha scritto:
> >> When we tried at first to generate the schema file using the jdbc 
task,
> >> we found that the database name put in the schema file was wrong.
> >> Instead of the db name there was the  username used to connect to the 

> >> 
> > db.
> > 
> >> We worked around it changing the username.
> >>
> >> We use Torque 3.3
> >> The DB server is postgres8.3
> >> The jdbc driver is postgresql-8.3-603.jdbc4.jar
> >> 
> >
> > There was a discussion way back on the user list (or maybe even in 
jira) 
> > of how the database should be named by the jdbc task. And the outcome 
was: 
> > how should the generator know ? Not every database has the concept of 
a 
> > database name. And jdbc won't provide that information anyway. So 
using 
> > the user name seems a sensible default.



      
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message