I have never meant this: I was only surprised you have been so
responsive on the mailing list and that there was no activity on jira.
Moreover I was surprised to find the issue already set and so old after
you had asked me to report it.
No problem, anyway.
Thomas Fischer ha scritto:
Sorry to
Sorry to come back on this issue: I have updated the TORQUE-39 issue on
jira but I have seen no answer to the observations I have added to the
initial ones.
I report here the link to the issue for whoever is interested:
https://issues.apache.org/jira/browse/TORQUE-39
Thomas Fischer ha
Sorry to come back on this issue: I have updated the TORQUE-39 issue on
jira but I have seen no answer to the observations I have added to the
initial ones.
I report here the link to the issue for whoever is interested:
Hey, this is no commercial product where we meet deadlines. It will
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/__
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
