Thank you Greg I have found the docs on schema files.
For what it worths, I will put my 2 cents on the Torque vs Hibernate matter.
Usually you don't want to overwrite your sql if you are not in the early
steps of db development: you change the DDL saving the data in some way.
The utility of
My personal opinion is that there are two reasons:
1) documentation is _MUCH_ better for hibernate
2) The concept for hibernate seems to be easy: Give an object to
Hibernate
and Hibernate does all the persistence work.
I'd like to add that I tend to disagree with the point easy
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
h, but then why make the torque user able to specify the
torque.database.name
property in build.properties ?
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
I certainly will, thanks
Thomas Fischer ha scritto:
h, 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
_
_ http://www.archicoop.it/__
Is there a way to configure Torque generator so that it generates om
classes only for a subset of the tables in a db ?
I will use the ability of torque tu support multiple database to import
some data from a secondary db, but I need to use only a small subset of
tables (5 out of 40+) of the whole
h, 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
Is there a way to configure Torque generator so that it generates om
classes only for a subset of the tables in a db ?
I will use the ability of torque tu support multiple database to import
some data from a secondary db, but I need to use only a small subset of
tables (5 out of 40+) of the
I once did that creating a new schema XML file and including in it only the
tables I wanted to import. In fact I had Torque create it automatically, and
then deleted the ones I didn't want.
Hope it helps,
Álvaro.
From: Ivano Luberti lube...@archicoop.it
To:
Ivano Luberti wrote:
Then, given your answer about the limitations of the jdbc task, I think
that the absence of some visual tool that is able to produce this schema
files is something that prevents Torque to be more successful.
For example if Power Architect would be able to generate both
10 matches
Mail list logo
