So, after the 5.0 release, it is finally time to say goodbye and to unsubscribe
from the torqe lists. Thanks for the time I have been allowed to work with you
and contribute to Torque! If you have any particular questions about the code I
wrote or anything else you feel I can answer, you are alw
Dear Torque developers,
after all the years, I've noticed that I do not have the drive, energy and time
to participate any more in the Torque development. Thus, after the 5.0 release
is out (in case my vote is needed, though that is not critical anymore (thanks
Thomas V!)), I'll make my retirem
e to the PMC mailing list.
Thomas (Fox)
- Ursprüngliche Mail -
Von: "Georg Kallidis"
An: "Apache Torque Developers List"
Gesendet: Sonntag, 30. August 2020 21:31:22
Betreff: Re: Re: Re: [VOTE] RC Torque 5.0 based on staged repository #DNSBL#
Hi Jeffery, hi Torque
Though I do not know about any blocking Jira issues, a 4.1 release would be
great.
Don't know about the version number, for me 4.1 seems a good version number in
terms of semantic versioning, but I'm open to other version numbers.
Thomas F.
- Ursprüngliche Mail -
Von: "Georg Kallidi
Very cool.
Thanks, Thomas
Thomas
smime.p7s
Description: S/MIME Cryptographic Signature
Thanks, Thomas, looks good. +1
Cheers,
Thomas
smime.p7s
Description: S/MIME Cryptographic Signature
There is
/torque-test/src/main/torque-gen/templates/peer/base/classAnnotations.vm in the
test project.
The intention was to verify that generation can be changed within a project. Is
that what you mean?
Perhaps the best idea is to replace the annotations with some comment?
Thomas
- U
On 9. 7. 2018, Thomas Vandahl wrote:
> On 9/6/18 7:03 AM, Thomas Fox wrote:
> > Ok, but should we not reset the committed and rolledBack Flag when the user
> > could have issued further statements after a commit/rollback, e.g. when
> > connection.createStatement() ist call
> Drop support for commons-dbcp 1?
+1
I see no harm in it. One can still use 4.0 if one wants this support.
Thomas
-
Dr. Thomas Fox
Lead Software Developer
Tel +49 (0) 7531 36598-22
Fax +49 (0) 7
On 5.09.2018 19:07, Thomas Vandahl wrote:
>On 03.09.18 04:32, Thomas Fox wrote:
>> Hi Thomas,
>>
>> Sure you want to format code like
>>
>> private static final LoadExternalSchemaTransformer
>> loadExternalSchemaTransformer
>> = new LoadE
On 05.09.18 19:30, Thomas Vandahl wrote:
> On 05.09.18 19:19, Thomas Vandahl wrote:
>> On 03.09.18 05:32, Thomas Fox wrote:
>>> As I understand it, TorqueConnectionImpl.committed and
>>> TorqueConnectionImpl.rolledBack keep track of whether there could be
>
Thomas,
I'm sorry but I do not understand the state kept in TorqueConnectionImpl.
As I understand it, TorqueConnectionImpl.committed and
TorqueConnectionImpl.rolledBack keep track of whether there could be
outstanding operations in a transaction. So when one calls close() on a
connection with
Hi Thomas,
Sure you want to format code like
private static final LoadExternalSchemaTransformer
loadExternalSchemaTransformer
= new LoadExternalSchemaTransformer();
instead of
private static final LoadExternalSchemaTransformer
loadExternalSchemaTransformer
= new Lo
+1
Thomas
- Ursprüngliche Mail -
Von: "tv"
An: "Apache Torque Developers List"
Gesendet: Freitag, 27. April 2018 11:31:24
Betreff: [VOTE] New Torque Committers: Georg Kallidis and Jeffery Painter
Hi folks,
two people from the Turbine project have shown interest to help with a
new rele
3 - in /db/torque/torque4/trunk: pom.xml
torque-generator/pom.xml torque-test/pom.xml
Hi Thomas,
On 19.09.16 22:02, Thomas Fox wrote:
> Thomas, you have removed some version number from the maven plugins poms.
> I'm aware that the version number of the plugins were not the most current
&g
Thomas, you have removed some version number from the maven plugins poms.
I'm aware that the version number of the plugins were not the most current
ones:-)
However, I have found that specifying version numbers of plugins makes a maven
build much more stable and reproducable.
If the only intentio
Thomas, is it ok if I remove the empty templates
doSelect.vm
doInsert.vm
log.vm
and the commented lines in imports.vm?
Also it seems to me that the generation option
torque.om.addSelectSingleRecordMethods
does not make sensae anymore as it's only used in the static wrapper- the
implementation m
+1 for moving to java 8
Thomas
- Ursprüngliche Mail -
Von: "tv"
An: "Apache Torque Developers List"
Gesendet: Freitag, 5. August 2016 12:43:05
Betreff: Java 7 or 8 for Torque Runtime?
Hi folks,
isn't it time to upgrade to a more recent JDK for the Torque runtime?
I could imagine som
[
https://issues.apache.org/jira/browse/TORQUE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400384#comment-15400384
]
Thomas Fox commented on TORQUE-343:
---
Sorry for pestering you with questions. Go a
[
https://issues.apache.org/jira/browse/TORQUE-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400381#comment-15400381
]
Thomas Fox commented on TORQUE-346:
---
I'm not sure what you mena by "ava
[
https://issues.apache.org/jira/browse/TORQUE-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395060#comment-15395060
]
Thomas Fox commented on TORQUE-346:
---
In a normal Torque setup, if you
[
https://issues.apache.org/jira/browse/TORQUE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395057#comment-15395057
]
Thomas Fox commented on TORQUE-343:
---
Let me see if I grasp the fulcrum case:
- Ther
[
https://issues.apache.org/jira/browse/TORQUE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1524#comment-1524
]
Thomas Fox commented on TORQUE-343:
---
You can already dynamically extend and exch
[
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
[
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 an
[
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
[
https://issues.apache.org/jira/browse/TORQUE-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174391#comment-15174391
]
Thomas Fox commented on TORQUE-342:
---
Removing the throws clause in generation can b
[
https://issues.apache.org/jira/browse/TORQUE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970604#comment-14970604
]
Thomas Fox commented on TORQUE-108:
---
If you want, can you provide your test so it
[
https://issues.apache.org/jira/browse/TORQUE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953659#comment-14953659
]
Thomas Fox commented on TORQUE-340:
---
If I did not overlook something,
[
https://issues.apache.org/jira/browse/TORQUE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952537#comment-14952537
]
Thomas Fox commented on TORQUE-337:
---
Though I can see the need for overriding
[
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
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
[
https://issues.apache.org/jira/browse/TORQUE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fox resolved TORQUE-341.
---
Resolution: Fixed
> Make PreparedStatementPart an interf
[
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
convention for any future convenience method.. e.g.
retrieveByStringPKs and the like.
On 9/19/15 5:02 PM, Thomas Fox wrote:
> Hi,
>
> for
> https://issues.apache.org/jira/browse/TORQUE-334
> I'd like to change the name of the existing retriebeByPks methods to
> retrie
[
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
[
https://issues.apache.org/jira/browse/TORQUE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900055#comment-14900055
]
Thomas Fox commented on TORQUE-338:
---
The problem is that e.g. with maven, by def
[
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 genera
Hi,
for
https://issues.apache.org/jira/browse/TORQUE-334
I'd like to change the name of the existing retriebeByPks methods to
retrieveByObjectKeys.
Any objections or better ideas ?
Example:
BaseBookPeer now has 2 methods:
public static List retrieveByPKs(Collection pks);
public static List re
[
https://issues.apache.org/jira/browse/TORQUE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14877319#comment-14877319
]
Thomas Fox commented on TORQUE-334:
---
An alternative would be to change the name of
[
https://issues.apache.org/jira/browse/TORQUE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14877312#comment-14877312
]
Thomas Fox commented on TORQUE-334:
---
A different name must be used for the new me
[
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
[
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
[
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
[
https://issues.apache.org/jira/browse/TORQUE-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14877288#comment-14877288
]
Thomas Fox commented on TORQUE-226:
---
We proceed by using the new jgit version
Hi,
in order to solve
https://issues.apache.org/jira/browse/TORQUE-290
I'd like to make org.apache.torque.criteria.PreparedStatementPart an interface
with the current PreparedStatementPart being renamed to
PreparedStatementPartImpl
and an implementation of that interface.
As the class is in the
Thanks, Thomas.
I have resolved the corresponding jira issue,
https://issues.apache.org/jira/browse/TORQUE-327
Thomas
- Ursprüngliche Mail -
Von: "Thomas Vandahl"
An: "Apache Torque Developers List"
Gesendet: Freitag, 11. September 2015 16:22:27
Betreff: Re: Upgrade to JCS-20-beta
[
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
[
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
[
https://issues.apache.org/jira/browse/TORQUE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fox reassigned TORQUE-327:
-
Assignee: Thomas Vandahl
> Upgrade to JCS-2.0
> ---
>
>
Betreff: Re: Upgrade to JCS-20-beta1
On 05.09.15 07:51, Thomas Fox wrote:
> We have an open ticket
> https://issues.apache.org/jira/browse/TORQUE-327
> which suggests to upgrade to JCS 2.0. Now JCS-2.0-beta1 is available. Does
> anyone have an idea how stable this version ist and whethe
[
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
[
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
We have an open ticket
https://issues.apache.org/jira/browse/TORQUE-327
which suggests to upgrade to JCS 2.0. Now JCS-2.0-beta1 is available. Does
anyone have an idea how stable this version ist and whether we should try to
use it ?
Thanks,
Thomas
--
[
https://issues.apache.org/jira/browse/TORQUE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fox resolved TORQUE-306.
---
Resolution: Fixed
Fix Version/s: 4.1
> Use named variables for replaceme
Hi,
for fixing https://issues.apache.org/jira/browse/TORQUE-226, a version of jgit
must be included which requires JDK 1.7 for the generator.
I suggest to raise the required JDK version for the Torque 4.1 generator to JDK
1.7
Also, it has become difficult to run a JDK 1.5 build on the Apache bu
[
https://issues.apache.org/jira/browse/TORQUE-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731691#comment-14731691
]
Thomas Fox commented on TORQUE-226:
---
This is fixed in jgit version 4.0.1.2015062402
[
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
[
https://issues.apache.org/jira/browse/TORQUE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617843#comment-14617843
]
Thomas Fox commented on TORQUE-108:
---
This problem is fixed in 4.0. I am not
[
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 datab
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
[
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
[
https://issues.apache.org/jira/browse/TORQUE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184484#comment-14184484
]
Thomas Fox commented on TORQUE-290:
---
There are two strategies to address the proble
[
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, Criter
Thomas Fox created TORQUE-333:
-
Summary: Criteria.addJoin(PreparedStatementPart,
PreparedStatementPart, Criterion, JoinTpye) discards replacements
Key: TORQUE-333
URL: https://issues.apache.org/jira/browse/TORQUE
[
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
[
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 defa
[
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
[
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
[
https://issues.apache.org/jira/browse/TORQUE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184375#comment-14184375
]
Thomas Fox commented on TORQUE-331:
---
For being able to use enum values in select
[
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 possi
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
[
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
[
https://issues.apache.org/jira/browse/TORQUE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165881#comment-14165881
]
Thomas Fox commented on TORQUE-331:
---
If possible, a constraint should be generate
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
[
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 documentation/orm
[
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 documentat
[
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 bet
[
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, dou
[
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
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
[
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
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
[
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 crite
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
[
https://issues.apache.org/jira/browse/TORQUE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fox reassigned TORQUE-320:
-
Assignee: Thomas Fox
> GroupBy adds columns to the select cla
[
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
[
https://issues.apache.org/jira/browse/TORQUE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145667#comment-14145667
]
Thomas Fox commented on TORQUE-323:
---
Note: in current trunk the schema locateion
[
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
[
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, INTERS
[
https://issues.apache.org/jira/browse/TORQUE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126268#comment-14126268
]
Thomas Fox commented on TORQUE-322:
---
According to http://en.wikipedia.org/
[
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, INTERS
[
https://issues.apache.org/jira/browse/TORQUE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fox resolved TORQUE-326.
---
Resolution: Fixed
> Setters in Criterion can be used for composite Criter
Thomas Fox created TORQUE-326:
-
Summary: Setters in Criterion can be used for composite Criterion
Key: TORQUE-326
URL: https://issues.apache.org/jira/browse/TORQUE-326
Project: Torque
Issue Type
[
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 f
[
https://issues.apache.org/jira/browse/TORQUE-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fox resolved TORQUE-313.
---
Resolution: Fixed
This was probably resoved by fixing TORQUE-291 or TORQUE-315.
There are several
[
https://issues.apache.org/jira/browse/TORQUE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fox resolved TORQUE-308.
---
Resolution: Fixed
Fix Version/s: 4.1
Assignee: Thomas Fox
> wrong schema location
[
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
[
https://issues.apache.org/jira/browse/TORQUE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124586#comment-14124586
]
Thomas Fox commented on TORQUE-317:
---
The same for useManagers, this switch is
[
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 obje
1 - 100 of 971 matches
Mail list logo
