[jira] [Commented] (TORQUE-343) Implement a central registry for peerImpls like the registry for managers

[ https://issues.apache.org/jira/browse/TORQUE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15400384#comment-15400384 ] Thomas Fox commented on TORQUE-343: --- Sorry for pestering you with questions. Go ahead. I'm just

[jira] [Commented] (TORQUE-346) Introduce abstract layer for peer impl to reduce the amount of generated code

[ https://issues.apache.org/jira/browse/TORQUE-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15400381#comment-15400381 ] Thomas Fox commented on TORQUE-346: --- I'm not sure what you mena by "availability of a primary key". If

[jira] [Commented] (TORQUE-343) Implement a central registry for peerImpls like the registry for managers

[ https://issues.apache.org/jira/browse/TORQUE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395057#comment-15395057 ] Thomas Fox commented on TORQUE-343: --- Let me see if I grasp the fulcrum case: - There is a FulcrumUser

[jira] [Commented] (TORQUE-343) Implement a central registry for peerImpls like the registry for managers

[ https://issues.apache.org/jira/browse/TORQUE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1524#comment-1524 ] Thomas Fox commented on TORQUE-343: --- You can already dynamically extend and exchange the PeerImpls by

[jira] [Closed] (TORQUE-295) The configuration of the generator should be simplified

[ https://issues.apache.org/jira/browse/TORQUE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox closed TORQUE-295. - Resolution: Fixed Fix Version/s: 4.1 Unfortunately, no big possibilities for simplification were

[jira] [Closed] (TORQUE-281) Only issue SQL update with columns whose value is changed in dbObject, since it was loaded from db

[ https://issues.apache.org/jira/browse/TORQUE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox closed TORQUE-281. - Resolution: Won't Fix Still nobyody wh wants to implement this. Please reopen the ticket if anybody

[jira] [Closed] (TORQUE-340) Not all DBCP properties are supported for connection pools

[ https://issues.apache.org/jira/browse/TORQUE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox closed TORQUE-340. - Resolution: Cannot Reproduce Closing due to lack of response. Please reopen if there are any new insights

[jira] [Commented] (TORQUE-342) XXXPeer.addSelectColumns() is declared to throw TorqueException for no apparent reason

[ https://issues.apache.org/jira/browse/TORQUE-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174391#comment-15174391 ] Thomas Fox commented on TORQUE-342: --- Removing the throws clause in generation can break compiletime

[jira] [Commented] (TORQUE-108) Criteria addJoin causes incorrect SQL to be generated when optional schema references are in use (Oracle)

[ https://issues.apache.org/jira/browse/TORQUE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14970604#comment-14970604 ] Thomas Fox commented on TORQUE-108: --- If you want, can you provide your test so it can be added to the

[jira] [Commented] (TORQUE-340) Not all DBCP properties are supported for connection pools

[ https://issues.apache.org/jira/browse/TORQUE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14953659#comment-14953659 ] Thomas Fox commented on TORQUE-340: --- If I did not overlook something, the connectionInitSqls attribute

[jira] [Commented] (TORQUE-337) Add ability to easily configure logging for the generator

[ https://issues.apache.org/jira/browse/TORQUE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14952537#comment-14952537 ] Thomas Fox commented on TORQUE-337: --- Though I can see the need for overriding the internal log

[jira] [Resolved] (TORQUE-334) retrieveByPKs(simpleType) should also be generated

[ https://issues.apache.org/jira/browse/TORQUE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-334. --- Resolution: Fixed Fix Version/s: 4.1 solution (thanks to Greg Monroe for the suggestion): -

[jira] [Created] (TORQUE-341) Make PreparedStatementPart an interface

Thomas Fox created TORQUE-341: - Summary: Make PreparedStatementPart an interface Key: TORQUE-341 URL: https://issues.apache.org/jira/browse/TORQUE-341 Project: Torque Issue Type: Sub-task

[jira] [Resolved] (TORQUE-290) Improve building from clause in subselect

[ https://issues.apache.org/jira/browse/TORQUE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-290. --- Resolution: Fixed Fix Version/s: 4.1 A Mixture between Strategy 1 and 2 was used. A special

[jira] [Commented] (TORQUE-338) Fix the saving of checksums when runOnlyOnSourceChange is set to true

[ https://issues.apache.org/jira/browse/TORQUE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14900055#comment-14900055 ] Thomas Fox commented on TORQUE-338: --- The problem is that e.g. with maven, by default, the same cache dir

[jira] [Resolved] (TORQUE-338) Fix the saving of checksums when runOnlyOnSourceChange is set to true

[ https://issues.apache.org/jira/browse/TORQUE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-338. --- Resolution: Fixed Assignee: Thomas Fox Fix Version/s: 4.1 Thanks, patch was applied.

[jira] [Assigned] (TORQUE-334) retrieveByPKs(simpleType) should also be generated

[ https://issues.apache.org/jira/browse/TORQUE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox reassigned TORQUE-334: - Assignee: Thomas Fox > retrieveByPKs(simpleType) should also be generated >

[jira] [Commented] (TORQUE-334) retrieveByPKs(simpleType) should also be generated

[ https://issues.apache.org/jira/browse/TORQUE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14877312#comment-14877312 ] Thomas Fox commented on TORQUE-334: --- A different name must be used for the new method as it would have

[jira] [Updated] (TORQUE-334) retrieveByPKs(simpleType) should also be generated

[ https://issues.apache.org/jira/browse/TORQUE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox updated TORQUE-334: -- Description: Currently, there is a retrieveByPKs(Collection) method. But if e.g. the PK is of type

[jira] [Commented] (TORQUE-334) retrieveByPKs(simpleType) should also be generated

[ https://issues.apache.org/jira/browse/TORQUE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14877319#comment-14877319 ] Thomas Fox commented on TORQUE-334: --- An alternative would be to change the name of the existing methods

[jira] [Commented] (TORQUE-226) The existing target mode "merge" has problems with files without line break at end of file

[ https://issues.apache.org/jira/browse/TORQUE-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14877288#comment-14877288 ] Thomas Fox commented on TORQUE-226: --- We proceed by using the new jgit version and upgrading to jdk 1.7

[jira] [Updated] (TORQUE-334) retrieveByPKs(simpleType) should also be generated

[ https://issues.apache.org/jira/browse/TORQUE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox updated TORQUE-334: -- Description: Currently, there is a retriveByPKs(Collection>ObjectKey) method. But if e.g. the PK is of

[jira] [Resolved] (TORQUE-226) The existing target mode "merge" has problems with files without line break at end of file

[ https://issues.apache.org/jira/browse/TORQUE-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-226. --- Resolution: Fixed Fix Version/s: 4.1 > The existing target mode "merge" has problems with

[jira] [Resolved] (TORQUE-327) Upgrade to JCS-2.0

[ https://issues.apache.org/jira/browse/TORQUE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-327. --- Resolution: Fixed > Upgrade to JCS-2.0 > --- > > Key: TORQUE-327 >

[jira] [Updated] (TORQUE-327) Upgrade to JCS-2.0

[ https://issues.apache.org/jira/browse/TORQUE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox updated TORQUE-327: -- Fix Version/s: 4.1 > Upgrade to JCS-2.0 > --- > > Key: TORQUE-327 >

[jira] [Resolved] (TORQUE-339) Correct the order of outlet and mergepoint in the last example of the configuration section of the code generation documentation

[ https://issues.apache.org/jira/browse/TORQUE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-339. --- Resolution: Fixed Assignee: (was: Thomas Fox) Fix Version/s: 4.1 > Correct the

[jira] [Assigned] (TORQUE-339) Correct the order of outlet and mergepoint in the last example of the configuration section of the code generation documentation

[ https://issues.apache.org/jira/browse/TORQUE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox reassigned TORQUE-339: - Assignee: Thomas Fox > Correct the order of outlet and mergepoint in the last example of the >

[jira] [Resolved] (TORQUE-203) Quote table names in creation

[ https://issues.apache.org/jira/browse/TORQUE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-203. --- Resolution: Won't Fix Resolved as won't fix as no workable solution has come up. Please reopen if

[jira] [Commented] (TORQUE-108) Criteria addJoin causes incorrect SQL to be generated when optional schema references are in use (Oracle)

[ https://issues.apache.org/jira/browse/TORQUE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14617843#comment-14617843 ] Thomas Fox commented on TORQUE-108: --- This problem is fixed in 4.0. I am not sure whether

[jira] [Resolved] (TORQUE-336) Incorrect schema location in documentation and database-4-0-strict.xsd

[ https://issues.apache.org/jira/browse/TORQUE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-336. --- Resolution: Fixed Fix Version/s: 4.1 Incorrect schema location in documentation and

[jira] [Created] (TORQUE-334) retrieveByPKs(simpleType) should also be generated

Thomas Fox created TORQUE-334: - Summary: retrieveByPKs(simpleType) should also be generated Key: TORQUE-334 URL: https://issues.apache.org/jira/browse/TORQUE-334 Project: Torque Issue Type: Bug

[jira] [Resolved] (TORQUE-269) Offline docs do not contain xsd files

[ https://issues.apache.org/jira/browse/TORQUE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-269. --- Resolution: Fixed Fix Version/s: 4.1 Assignee: Thomas Fox Offline docs do not

[jira] [Updated] (TORQUE-332) Criteria.addJoin(String, String, Criterion, JoinType) does not honor default schema

[ https://issues.apache.org/jira/browse/TORQUE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox updated TORQUE-332: -- Summary: Criteria.addJoin(String, String, Criterion, JoinType) does not honor default schema (was:

[jira] [Resolved] (TORQUE-332) Criteria.addJoin(String, String, Criterion, JoinType) does not honor default schema

[ https://issues.apache.org/jira/browse/TORQUE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-332. --- Resolution: Fixed Criteria.addJoin(String, String, Criterion, JoinType) does not honor default

[jira] [Updated] (TORQUE-332) Criteria.addJoin(String, String, Criterion, JoinType) does not honor default schema

[ https://issues.apache.org/jira/browse/TORQUE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox updated TORQUE-332: -- Description: Situation: A Default schema is set in Torque, i.e. all Table names should be prefixed

[jira] [Updated] (TORQUE-290) Improve building from clause in subselect

[ https://issues.apache.org/jira/browse/TORQUE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox updated TORQUE-290: -- Description: Currently, it is not easily possible to reference columns in the main select from a

[jira] [Created] (TORQUE-333) Criteria.addJoin(PreparedStatementPart, PreparedStatementPart, Criterion, JoinTpye) discards replacements

Thomas Fox created TORQUE-333: - Summary: Criteria.addJoin(PreparedStatementPart, PreparedStatementPart, Criterion, JoinTpye) discards replacements Key: TORQUE-333 URL:

[jira] [Resolved] (TORQUE-333) Criteria.addJoin(PreparedStatementPart, PreparedStatementPart, Criterion, JoinTpye) discards replacements

[ https://issues.apache.org/jira/browse/TORQUE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-333. --- Resolution: Fixed Criteria.addJoin(PreparedStatementPart, PreparedStatementPart, Criterion,

[jira] [Commented] (TORQUE-290) Improve building from clause in subselect

[ https://issues.apache.org/jira/browse/TORQUE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184484#comment-14184484 ] Thomas Fox commented on TORQUE-290: --- There are two strategies to address the problem: 1)

[jira] [Resolved] (TORQUE-331) Make enum generation possible

[ https://issues.apache.org/jira/browse/TORQUE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-331. --- Resolution: Fixed Make enum generation possible -

[jira] [Commented] (TORQUE-331) Make enum generation possible

[ https://issues.apache.org/jira/browse/TORQUE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184375#comment-14184375 ] Thomas Fox commented on TORQUE-331: --- For being able to use enum values in select like

[jira] [Created] (TORQUE-332) Criteria.addJoin(String, String, Criteria) does not honor default schema

Thomas Fox created TORQUE-332: - Summary: Criteria.addJoin(String, String, Criteria) does not honor default schema Key: TORQUE-332 URL: https://issues.apache.org/jira/browse/TORQUE-332 Project: Torque

[jira] [Created] (TORQUE-331) Make enum generation possible

Thomas Fox created TORQUE-331: - Summary: Make enum generation possible Key: TORQUE-331 URL: https://issues.apache.org/jira/browse/TORQUE-331 Project: Torque Issue Type: New Feature

[jira] [Commented] (TORQUE-331) Make enum generation possible

[ https://issues.apache.org/jira/browse/TORQUE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14165881#comment-14165881 ] Thomas Fox commented on TORQUE-331: --- If possible, a constraint should be generated on

[jira] [Updated] (TORQUE-331) Make enum generation possible

[ https://issues.apache.org/jira/browse/TORQUE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox updated TORQUE-331: -- Description: It should be possible to generate an enum for a value. In the schema, this would look like

[jira] [Updated] (TORQUE-329) Create better schema documentation

[ https://issues.apache.org/jira/browse/TORQUE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox updated TORQUE-329: -- Summary: Create better schema documentation (was: Create better schema documentaion) Create better

[jira] [Assigned] (TORQUE-329) Create better schema documentation

[ https://issues.apache.org/jira/browse/TORQUE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox reassigned TORQUE-329: - Assignee: Thomas Fox Create better schema documentation --

[jira] [Resolved] (TORQUE-329) Create better schema documentation

[ https://issues.apache.org/jira/browse/TORQUE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-329. --- Resolution: Fixed Fix Version/s: 4.1 Added a schema reference to the

[jira] [Created] (TORQUE-330) Postgresql fails for some prepared statement replacement types (short, double ...)

Thomas Fox created TORQUE-330: - Summary: Postgresql fails for some prepared statement replacement types (short, double ...) Key: TORQUE-330 URL: https://issues.apache.org/jira/browse/TORQUE-330 Project:

[jira] [Updated] (TORQUE-330) Postgresql fails for some prepared statement replacement types (short, double ...)

[ https://issues.apache.org/jira/browse/TORQUE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox updated TORQUE-330: -- Description: When executing a SQL statement with some prepared statement replacement types

[jira] [Resolved] (TORQUE-330) Postgresql fails for some prepared statement replacement types (short, double ...)

[ https://issues.apache.org/jira/browse/TORQUE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-330. --- Resolution: Fixed Postgresql fails for some prepared statement replacement types (short, double

[jira] [Created] (TORQUE-329) Create better schema documentaion

Thomas Fox created TORQUE-329: - Summary: Create better schema documentaion Key: TORQUE-329 URL: https://issues.apache.org/jira/browse/TORQUE-329 Project: Torque Issue Type: Improvement

[jira] [Resolved] (TORQUE-320) GroupBy adds columns to the select clause

[ https://issues.apache.org/jira/browse/TORQUE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-320. --- Resolution: Fixed Fix Version/s: 4.1 I have created a test case in the test project which

[jira] [Resolved] (TORQUE-278) There should not be a create table command in the generated sql for tables from a external schema

[ https://issues.apache.org/jira/browse/TORQUE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-278. --- Resolution: Fixed Fix Version/s: 4.1 There should not be a create table command in the

[jira] [Commented] (TORQUE-323) Error in schema.xml for cascade=none with postgresql

[ https://issues.apache.org/jira/browse/TORQUE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14145667#comment-14145667 ] Thomas Fox commented on TORQUE-323: --- Note: in current trunk the schema locateion has

[jira] [Resolved] (TORQUE-323) Error in schema.xml for cascade=none with postgresql

[ https://issues.apache.org/jira/browse/TORQUE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-323. --- Resolution: Cannot Reproduce Assignee: Thomas Fox I cannot reproduce the described behaviour.

[jira] [Created] (TORQUE-328) Use builder pattern throughout criteria

Thomas Fox created TORQUE-328: - Summary: Use builder pattern throughout criteria Key: TORQUE-328 URL: https://issues.apache.org/jira/browse/TORQUE-328 Project: Torque Issue Type: Bug

[jira] [Resolved] (TORQUE-328) Use builder pattern throughout criteria

[ https://issues.apache.org/jira/browse/TORQUE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-328. --- Resolution: Fixed Use builder pattern throughout criteria ---

[jira] [Resolved] (TORQUE-322) Support for SQL Set Operations (UNION, INTERSECT, ...)

[ https://issues.apache.org/jira/browse/TORQUE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-322. --- Resolution: Fixed Fix Version/s: 4.1 Support for SQL Set Operations (UNION, INTERSECT, ...)

[jira] [Assigned] (TORQUE-322) Support for SQL Set Operations (UNION, INTERSECT, ...)

[ https://issues.apache.org/jira/browse/TORQUE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox reassigned TORQUE-322: - Assignee: Thomas Fox Support for SQL Set Operations (UNION, INTERSECT, ...)

[jira] [Commented] (TORQUE-322) Support for SQL Set Operations (UNION, INTERSECT, ...)

[ https://issues.apache.org/jira/browse/TORQUE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126268#comment-14126268 ] Thomas Fox commented on TORQUE-322: --- According to

[jira] [Commented] (TORQUE-317) BaseBean does generate fields for referencing objects

[ https://issues.apache.org/jira/browse/TORQUE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14124586#comment-14124586 ] Thomas Fox commented on TORQUE-317: --- The same for useManagers, this switch is also

[jira] [Assigned] (TORQUE-281) Only issue SQL update with columns whose value is changed in dbObject, since it was loaded from db

[ https://issues.apache.org/jira/browse/TORQUE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox reassigned TORQUE-281: - Assignee: (was: Thomas Fox) Only issue SQL update with columns whose value is changed in

[jira] [Resolved] (TORQUE-315) setAndSave does not work if the cached collection from the object is passed in

[ https://issues.apache.org/jira/browse/TORQUE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-315. --- Resolution: Fixed Assignee: Thomas Fox setAndSave does not work if the cached collection from

[jira] [Commented] (TORQUE-317) BaseBean does generate fields for referencing objects

[ https://issues.apache.org/jira/browse/TORQUE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14121890#comment-14121890 ] Thomas Fox commented on TORQUE-317: --- It would be good if torque would ignore trailing

[jira] [Commented] (TORQUE-317) BaseBean does generate fields for referencing objects

[ https://issues.apache.org/jira/browse/TORQUE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14121963#comment-14121963 ] Thomas Fox commented on TORQUE-317: --- The only drawback is that the option is then not

[jira] [Resolved] (TORQUE-317) BaseBean does generate fields for referencing objects

[ https://issues.apache.org/jira/browse/TORQUE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-317. --- Resolution: Fixed Fix Version/s: 4.1 BaseBean does generate fields for referencing objects

[jira] [Created] (TORQUE-324) In the generator, the parent node should be referenceable with ..

Thomas Fox created TORQUE-324: - Summary: In the generator, the parent node should be referenceable with .. Key: TORQUE-324 URL: https://issues.apache.org/jira/browse/TORQUE-324 Project: Torque

[jira] [Resolved] (TORQUE-316) saveMethods.vm has toSave.setNew instead of a using toSaveVariableWithDot

[ https://issues.apache.org/jira/browse/TORQUE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-316. --- Resolution: Fixed Fix Version/s: 4.1 saveMethods.vm has toSave.setNew instead of a using

[jira] [Resolved] (TORQUE-318) retrieveByPK throws TorqueException instead of NoRowsException when it can't find a primary key.

[ https://issues.apache.org/jira/browse/TORQUE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-318. --- Resolution: Fixed Fix Version/s: 4.1 retrieveByPK throws TorqueException instead of

[jira] [Created] (TORQUE-325) Oracle sql files contain additional empty lines before ON DELETE token

Thomas Fox created TORQUE-325: - Summary: Oracle sql files contain additional empty lines before ON DELETE token Key: TORQUE-325 URL: https://issues.apache.org/jira/browse/TORQUE-325 Project: Torque

[jira] [Resolved] (TORQUE-325) Oracle sql files contain additional empty lines before ON DELETE token

[ https://issues.apache.org/jira/browse/TORQUE-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-325. --- Resolution: Fixed Assignee: Thomas Fox Oracle sql files contain additional empty lines before

[jira] [Commented] (TORQUE-312) NPE in generation process

[ https://issues.apache.org/jira/browse/TORQUE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14120322#comment-14120322 ] Thomas Fox commented on TORQUE-312: --- The supposed reason has been confirmed. NPE in

[jira] [Resolved] (TORQUE-321) Wrong optimization of iLike without wildcards

[ https://issues.apache.org/jira/browse/TORQUE-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-321. --- Resolution: Fixed Fix Version/s: 4.1 Wrong optimization of iLike without wildcards

[jira] [Resolved] (TORQUE-310) add simple way to remove unused imports

[ https://issues.apache.org/jira/browse/TORQUE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-310. --- Resolution: Fixed add simple way to remove unused imports ---

[jira] [Resolved] (TORQUE-311) wrong example configuration in docs

[ https://issues.apache.org/jira/browse/TORQUE-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-311. --- Resolution: Fixed Assignee: Thomas Fox wrong example configuration in docs

[jira] [Resolved] (TORQUE-319) No KEYS file; download page link is broken

[ https://issues.apache.org/jira/browse/TORQUE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-319. --- Resolution: Fixed No KEYS file; download page link is broken

[jira] [Assigned] (TORQUE-319) No KEYS file; download page link is broken

[ https://issues.apache.org/jira/browse/TORQUE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox reassigned TORQUE-319: - Assignee: Thomas Fox No KEYS file; download page link is broken

[jira] [Commented] (TORQUE-317) BaseBean does generate fields for referencing objects

[ https://issues.apache.org/jira/browse/TORQUE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14107483#comment-14107483 ] Thomas Fox commented on TORQUE-317: --- It could be that you have a trailing spaces

[jira] [Commented] (TORQUE-316) saveMethods.vm has toSave.setNew instead of a using toSaveVariableWithDot

[ https://issues.apache.org/jira/browse/TORQUE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14099776#comment-14099776 ] Thomas Fox commented on TORQUE-316: --- The proposed patch solves the problem. Thanks a

[jira] [Assigned] (TORQUE-317) BaseBean does generate fields for referencing objects

[ https://issues.apache.org/jira/browse/TORQUE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox reassigned TORQUE-317: - Assignee: Thomas Fox BaseBean does generate fields for referencing objects

[jira] [Assigned] (TORQUE-316) saveMethods.vm has toSave.setNew instead of a using toSaveVariableWithDot

[ https://issues.apache.org/jira/browse/TORQUE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox reassigned TORQUE-316: - Assignee: Thomas Fox saveMethods.vm has toSave.setNew instead of a using toSaveVariableWithDot

[jira] [Assigned] (TORQUE-312) NPE in generation process

[ https://issues.apache.org/jira/browse/TORQUE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox reassigned TORQUE-312: - Assignee: Thomas Fox NPE in generation process -

[jira] [Assigned] (TORQUE-321) Wrong optimization of iLike without wildcards

[ https://issues.apache.org/jira/browse/TORQUE-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox reassigned TORQUE-321: - Assignee: Thomas Fox Wrong optimization of iLike without wildcards

[jira] [Commented] (TORQUE-323) Error in schema.xml for cascade=none with postgresql

[ https://issues.apache.org/jira/browse/TORQUE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14099337#comment-14099337 ] Thomas Fox commented on TORQUE-323: --- I cannot reproduce the described behaviour. I have

[jira] [Commented] (TORQUE-320) GroupBy adds columns to the select clause

[ https://issues.apache.org/jira/browse/TORQUE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14099339#comment-14099339 ] Thomas Fox commented on TORQUE-320: --- Thomas, would an acceptable solution be having a

[jira] [Assigned] (TORQUE-318) retrieveByPK throws TorqueException instead of NoRowsException when it can't find a primary key.

[ https://issues.apache.org/jira/browse/TORQUE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox reassigned TORQUE-318: - Assignee: Thomas Fox The described behavior can also be seen in the test project

[jira] [Commented] (TORQUE-316) saveMethods.vm has toSave.setNew instead of a using toSaveVariableWithDot

[ https://issues.apache.org/jira/browse/TORQUE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14099402#comment-14099402 ] Thomas Fox commented on TORQUE-316: --- To reproduce the problem,

[jira] [Commented] (TORQUE-320) GroupBy adds columns to the select clause

[ https://issues.apache.org/jira/browse/TORQUE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075622#comment-14075622 ] Thomas Fox commented on TORQUE-320: --- I am not in favour of having different funtionality

[jira] [Commented] (TORQUE-319) No KEYS file; download page link is broken

[ https://issues.apache.org/jira/browse/TORQUE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074930#comment-14074930 ] Thomas Fox commented on TORQUE-319: --- The archived file is the correct one. Probably it

[jira] [Created] (TORQUE-320) GroupBy adds columns to the select clause

Thomas Fox created TORQUE-320: - Summary: GroupBy adds columns to the select clause Key: TORQUE-320 URL: https://issues.apache.org/jira/browse/TORQUE-320 Project: Torque Issue Type: Bug

[jira] [Created] (TORQUE-315) setAndSave does not work if the cached collection from the object is passed in

Thomas Fox created TORQUE-315: - Summary: setAndSave does not work if the cached collection from the object is passed in Key: TORQUE-315 URL: https://issues.apache.org/jira/browse/TORQUE-315 Project:

[jira] [Created] (TORQUE-314) filler methods do not set isNew and isModified flag correctly

Thomas Fox created TORQUE-314: - Summary: filler methods do not set isNew and isModified flag correctly Key: TORQUE-314 URL: https://issues.apache.org/jira/browse/TORQUE-314 Project: Torque

[jira] [Updated] (TORQUE-314) filler methods do not set isNew and isModified flag correctly

[ https://issues.apache.org/jira/browse/TORQUE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox updated TORQUE-314: -- Description: The objects read and returned by the generated filler methods are read directly from the

[jira] [Resolved] (TORQUE-314) filler methods do not set isNew and isModified flag correctly

[ https://issues.apache.org/jira/browse/TORQUE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox resolved TORQUE-314. --- Resolution: Fixed filler methods do not set isNew and isModified flag correctly

[jira] [Created] (TORQUE-313) setAndSave does not work with new objects

Thomas Fox created TORQUE-313: - Summary: setAndSave does not work with new objects Key: TORQUE-313 URL: https://issues.apache.org/jira/browse/TORQUE-313 Project: Torque Issue Type: Bug

[jira] [Assigned] (TORQUE-310) add simple way to remove unused imports

[ https://issues.apache.org/jira/browse/TORQUE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox reassigned TORQUE-310: - Assignee: Thomas Fox add simple way to remove unused imports

[jira] [Updated] (TORQUE-312) NPE in generation process

[ https://issues.apache.org/jira/browse/TORQUE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fox updated TORQUE-312: -- Component/s: Templates Generator NPE in generation process

[jira] [Created] (TORQUE-312) NPE in generation process

Thomas Fox created TORQUE-312: - Summary: NPE in generation process Key: TORQUE-312 URL: https://issues.apache.org/jira/browse/TORQUE-312 Project: Torque Issue Type: Bug Affects Versions: 4.0

[jira] [Created] (TORQUE-310) add simple way to remove unused imports

Thomas Fox created TORQUE-310: - Summary: add simple way to remove unused imports Key: TORQUE-310 URL: https://issues.apache.org/jira/browse/TORQUE-310 Project: Torque Issue Type: Bug

  1   2   3   4   5   6   >