You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by Thomas Vandahl <tv...@apache.org> on 2010/10/31 21:31:31 UTC
[VOTE] Release village-3.3.1 based on RC1
Hi folks,
A release candidate for village-3.3.1 has been prepared. This is a
Maven-2 build only. Please verify this release candidate and vote...
Tag:
https://svn.apache.org/repos/asf/db/torque/village/tags/VILLAGE_3_3_1
Site:
http://people.apache.org/~tv/torque/site/
Binaries:
http://people.apache.org/~tv/torque/
[ ] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: [VOTE] Release village-3.3.1 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
On 31.10.10 21:31, Thomas Vandahl wrote:
> [X] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because
To make a start.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: [VOTE] Release village-3.3.1 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
On 07.11.10 16:08, Thomas Fox wrote:
> Seems that invoking getMetadata() on a prepared statement that is not
> executed is not working in oracle (I am using 10.2.0.2.0). Adding
> statement.execute() before querying the metadata seems to fix the problem.
I was afraid of that. MySQL works fine. I found this as a recommended
method to save database hits, however. I guess it would be necessary to
move that to DatabaseMetaData as I did with the others. I'll give it one
more try.
> However, even when this is fixed there is a case sensitivity and table
> prefix issue in column names: e.g. village knows the column name
> author.AUTHOR_ID but the request is for author_id. This results in
> exceptions like
This is easy to fix.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
RE: [VOTE] Release village-3.3.1 based on RC1
Posted by Thomas Fox <Th...@seitenbau.net>.
I get exceptions on running the torque test project against oracle. E.G:
[junit] org.apache.torque.TorqueException: java.sql.SQLException:
Anweisungs-Handle nicht ausgef³hrt: getMetaData
[junit] at org.apache.torque.util.BasePeer.throwTorqueException
(BasePeer.java:106)
[junit] at org.apache.torque.util.BasePeer.doDelete
(BasePeer.java:438)
[junit] at org.apache.torque.util.BasePeer.doDelete
(BasePeer.java:337)
[junit] at org.apache.torque.test.BaseBookPeer.doDelete
(BaseBookPeer.java:516)
[junit] at org.apache.torque.test.BaseBookPeer.doDelete
(BaseBookPeer.java:493)
[junit] at org.apache.torque.BeanTestConditional.testSaves
(BeanTestConditional.java:276)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
[junit] Caused by: java.sql.SQLException: Anweisungs-Handle nicht
ausgef³hrt: getMetaData
[junit] at oracle.jdbc.driver.DatabaseError.throwSqlException
(DatabaseError.java:112)
[junit] at oracle.jdbc.driver.DatabaseError.throwSqlException
(DatabaseError.java:146)
[junit] at oracle.jdbc.driver.OracleResultSetImpl.getMetaData
(OracleResultSetImpl.java:135)
[junit] at oracle.jdbc.driver.OraclePreparedStatement.getMetaData
(OraclePreparedStatement.java:3985)
[junit] at com.workingdogs.village.Schema.schema(Schema.java:201)
[junit] at com.workingdogs.village.Schema.schema(Schema.java:151)
[junit] at com.workingdogs.village.DataSet.<init>(DataSet.java:153)
[junit] at com.workingdogs.village.TableDataSet.<init>
(TableDataSet.java:133)
[junit] at org.apache.torque.util.BasePeer.processTables
(BasePeer.java:1720)
[junit] at org.apache.torque.util.BasePeer.doDelete
(BasePeer.java:427)
[junit] ... 18 more
[junit]
[junit] Testcase: testSaves
Seems that invoking getMetadata() on a prepared statement that is not
executed is not working in oracle (I am using 10.2.0.2.0). Adding
statement.execute() before querying the metadata seems to fix the problem.
I know this has been in there quite some time and in the meantime I did run
the tests successfully against oracle (I write an email about it), but it
seems I was still using the 3.3.1 village version then :-(
However, even when this is fixed there is a case sensitivity and table
prefix issue in column names: e.g. village knows the column name
author.AUTHOR_ID but the request is for author_id. This results in
exceptions like
org.apache.torque.TorqueException:
com.workingdogs.village.DataSetException: Column name: author_id does not
exist!
at org.apache.torque.util.BasePeer.throwTorqueException
(BasePeer.java:106)
at org.apache.torque.util.BasePeer.insertOrUpdateRecord
(BasePeer.java:668)
at org.apache.torque.util.BasePeer.doInsert(BasePeer.java:563)
at org.apache.torque.test.BaseAuthorPeer.doInsert
(BaseAuthorPeer.java:221)
at org.apache.torque.test.BaseAuthorPeer.doInsert
(BaseAuthorPeer.java:570)
at org.apache.torque.test.BaseAuthor.save(BaseAuthor.java:585)
at org.apache.torque.test.BaseAuthor.save(BaseAuthor.java:549)
at org.apache.torque.test.BaseAuthor.save(BaseAuthor.java:530)
at org.apache.torque.DataTest.testInsertData(DataTest.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run
(JUnit3TestReference.java:130)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run
(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run
(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main
(RemoteTestRunner.java:197)
Caused by: com.workingdogs.village.DataSetException: Column name: author_id
does not exist!
at com.workingdogs.village.Schema.index(Schema.java:410)
at com.workingdogs.village.Record.setValue(Record.java:1134)
at org.apache.torque.util.VillageUtils.setVillageValue
(VillageUtils.java:212)
at org.apache.torque.util.BasePeer.insertOrUpdateRecord
(BasePeer.java:663)
... 23 more
Not sure if all test failures are caused by these two problems but they are
the most prominent problems.
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
RE: [VOTE] Release village-3.3.1 based on RC1
Posted by Thomas Fox <Th...@seitenbau.net>.
I'll check it this weekent, Sorry, do not have time before.
Thomas
> Von:
>
> Thomas Vandahl <tv...@apache.org>
>
> An:
>
> torque-dev@db.apache.org
>
> Datum:
>
> 31.10.2010 21:31
>
> Betreff:
>
> [VOTE] Release village-3.3.1 based on RC1
>
> Hi folks,
>
> A release candidate for village-3.3.1 has been prepared. This is a
> Maven-2 build only. Please verify this release candidate and vote...
>
> Tag:
>
> https://svn.apache.org/repos/asf/db/torque/village/tags/VILLAGE_3_3_1
>
> Site:
>
> http://people.apache.org/~tv/torque/site/
>
> Binaries:
>
> http://people.apache.org/~tv/torque/
>
>
> [ ] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because
>
> Bye, Thomas.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: [VOTE] Release village-3.3.1 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
On 10.11.10 21:44, Scott Eade wrote:
> I know in my apps I sometimes crack the egg and use Village.
Me, too. But I never went anywhere below Record, which I left unchanged.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: [VOTE] Release village-3.3.1 based on RC1
Posted by Scott Eade <se...@backstagetech.com.au>.
On 11/11/10 6:02 AM, Thomas Vandahl wrote:
> On 08.11.10 21:52, Scott Eade wrote:
>> Can we be sure that the changes made under heading "Removed all methods
>> from Column that are not actually used by Torque" are not going to
>> impact other users of Village? I haven't had the time to look at this
>> very carefully.
> I'm not aware of any uses outside of Torque.
I know in my apps I sometimes crack the egg and use Village. It would
have made more sense if we did a release with the bug fixes that was
100% backwards compatible followed by an update that may potentially not
maintain this compatibility.
I doubt if my applications venture so far into village that they would
be impacted and there are so few of us here that this should not have
any major impacts so I am not too concerned.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: [VOTE] Release village-3.3.1 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
On 08.11.10 21:52, Scott Eade wrote:
> Can we be sure that the changes made under heading "Removed all methods
> from Column that are not actually used by Torque" are not going to
> impact other users of Village? I haven't had the time to look at this
> very carefully.
I'm not aware of any uses outside of Torque.
This was planned to be a Torque-only-bugfix release. I thought to
prepare something for the Village-removal but Thomas Fox came up with a
proposal better than mine. Many of the features I removed were not
working correctly, anyway. It simplified a lot, too.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: [VOTE] Release village-3.3.1 based on RC1
Posted by Scott Eade <se...@backstagetech.com.au>.
Can we be sure that the changes made under heading "Removed all methods
from Column that are not actually used by Torque" are not going to
impact other users of Village? I haven't had the time to look at this
very carefully.
Scott
On 1/11/10 7:31 AM, Thomas Vandahl wrote:
> Hi folks,
>
> A release candidate for village-3.3.1 has been prepared. This is a
> Maven-2 build only. Please verify this release candidate and vote...
>
> Tag:
>
> https://svn.apache.org/repos/asf/db/torque/village/tags/VILLAGE_3_3_1
>
> Site:
>
> http://people.apache.org/~tv/torque/site/
>
> Binaries:
>
> http://people.apache.org/~tv/torque/
>
>
> [ ] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because
>
> Bye, Thomas.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
Re: [VOTE] Release village-3.3.1 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
On 01.11.10 19:02, Thomas Vandahl wrote:
> On 31.10.10 22:23, Scott Eade wrote:
>> What changed? There is no indication (that I can see) in the docs.
>
> There is http://people.apache.org/~tv/torque/site/changes.html but it
> looks a bit strange. :-) I'll try to fix the report and include it in
> the navigation.
See http://people.apache.org/~tv/torque/site/changes-report.html
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: [VOTE] Release village-3.3.1 based on RC1
Posted by Thomas Vandahl <tv...@apache.org>.
On 31.10.10 22:23, Scott Eade wrote:
> What changed? There is no indication (that I can see) in the docs.
There is http://people.apache.org/~tv/torque/site/changes.html but it
looks a bit strange. :-) I'll try to fix the report and include it in
the navigation.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: [VOTE] Release village-3.3.1 based on RC1
Posted by Scott Eade <se...@backstagetech.com.au>.
What changed? There is no indication (that I can see) in the docs.
Scott
On 1/11/10 7:31 AM, Thomas Vandahl wrote:
> Hi folks,
>
> A release candidate for village-3.3.1 has been prepared. This is a
> Maven-2 build only. Please verify this release candidate and vote...
>
> Tag:
>
> https://svn.apache.org/repos/asf/db/torque/village/tags/VILLAGE_3_3_1
>
> Site:
>
> http://people.apache.org/~tv/torque/site/
>
> Binaries:
>
> http://people.apache.org/~tv/torque/
>
>
> [ ] +1 release it
> [ ] +0 go ahead I don't care
> [ ] -1 no, do not release it because
>
> Bye, Thomas.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>