[
http://issues.apache.org/jira/browse/TORQUE-39?page=comments#action_12421539 ]
Thoralf Rickert commented on TORQUE-39:
---
Is it a big problem to hand over a property like torque.databaseName to the
task or to parse the property
Column names in generated classes are uppercase
---
Key: TORQUE-44
URL: http://issues.apache.org/jira/browse/TORQUE-44
Project: Torque
Issue Type: Bug
Components: Generator
[ http://issues.apache.org/jira/browse/TORQUE-44?page=all ]
Thoralf Rickert updated TORQUE-44:
--
Attachment: patch.txt
The problem is that the generator uses the variable
$cup=$col.Name.toUpperCase() for the name of the constant and for the content
of
[
http://issues.apache.org/jira/browse/TORQUE-45?page=comments#action_12421574 ]
Joe Carter commented on TORQUE-45:
--
So how are tables with circular references dropped?
Whatever the root cause, the underlying fault remains, in that you cannot
[
http://issues.apache.org/jira/browse/TORQUE-45?page=comments#action_12421580 ]
Thoralf Rickert commented on TORQUE-45:
---
So how are tables with circular references dropped?
I have this circular references problem in one of my schemes.
[
http://issues.apache.org/jira/browse/TORQUE-45?page=comments#action_12421585 ]
So how are tables with circular references dropped?
In some databases, there is the cascade constraints option to thge drop
table command which drops the constraints associated with the dropped
[
http://issues.apache.org/jira/browse/TORQUE-39?page=comments#action_12421708 ]
CG Monroe commented on TORQUE-39:
-
A couple of things to keep in mind about this.
First, the database tag name attribute is a Torque id and not actually tied to
