Re: Adding village 3.3.1to the torque site ?
On 03.03.11 11:38, Thomas Fox wrote: > > Anybody volunteering to add village 3.3.1 to the torqe site ? > In my opinion the release should be at least in the releases section on the > home page, on the "news and status" page and the download page. > > I can do the deploy as I'll need to do it anyway for the branding > requirements. I updated the xdoc files and committed them. For some reason my Maven-1 installation doesn't run the site goal anymore. Would you please check if I broke something? Bye, Thomas. - To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org For additional commands, e-mail: torque-dev-h...@db.apache.org
svn commit: r1078550 - in /db/torque/site/trunk/xdocs: download.xml index.xml status.xml
Author: tv Date: Sun Mar 6 19:46:13 2011 New Revision: 1078550 URL: http://svn.apache.org/viewvc?rev=1078550&view=rev Log: Added village 3.3.1 release and download information Modified: db/torque/site/trunk/xdocs/download.xml db/torque/site/trunk/xdocs/index.xml db/torque/site/trunk/xdocs/status.xml Modified: db/torque/site/trunk/xdocs/download.xml URL: http://svn.apache.org/viewvc/db/torque/site/trunk/xdocs/download.xml?rev=1078550&r1=1078549&r2=1078550&view=diff == --- db/torque/site/trunk/xdocs/download.xml (original) +++ db/torque/site/trunk/xdocs/download.xml Sun Mar 6 19:46:13 2011 @@ -44,6 +44,7 @@ The currently released versions of Torqu Runtime Generator Village + Village 3.3.1 Maven Plugin @@ -65,6 +66,11 @@ The currently released versions of Torqu http://www.apache.org/dist/db/torque/torque-3.3/binaries/village-3.3.tar.gz.md5";>MD5 + http://repo1.maven.org/maven2/org/apache/torque/village/3.3.1/village-3.3.1.jar";>JAR + http://repo1.maven.org/maven2/org/apache/torque/village/3.3.1/village-3.3.1.jar.asc";>Sig. + http://repo1.maven.org/maven2/org/apache/torque/village/3.3.1/village-3.3.1.jar.md5";>MD5 + + http://www.apache.org/dyn/closer.cgi/java-repository/torque/plugins/maven-torque-plugin-3.3.jar";>JAR http://www.apache.org/dist/java-repository/torque/plugins/maven-torque-plugin-3.3.jar.asc";>Sig. http://www.apache.org/dist/java-repository/torque/plugins/maven-torque-plugin-3.3.jar.md5";>MD5 @@ -99,6 +105,8 @@ The currently released versions of Torqu + + http://www.apache.org/dyn/closer.cgi/java-repository/torque/plugins/maven-torque-plugin-3.2.jar";>JAR http://www.apache.org/dist/java-repository/torque/plugins/maven-torque-plugin-3.2.jar.asc";>Sig. @@ -116,6 +124,8 @@ The currently released versions of Torqu + + @@ -130,6 +140,7 @@ The currently released versions of Torqu Runtime Generator Village + Village 3.3.1 Maven Plugin @@ -148,6 +159,11 @@ The currently released versions of Torqu http://www.apache.org/dist/db/torque/torque-3.3/source/village-3.3-src.tar.gz.asc";>Sig. http://www.apache.org/dist/db/torque/torque-3.3/source/village-3.3-src.tar.gz.md5";>MD5 + + http://repo1.maven.org/maven2/org/apache/torque/village/3.3.1/village-3.3.1-source.jar";>JAR + http://repo1.maven.org/maven2/org/apache/torque/village/3.3.1/village-3.3.1-source.jar.asc";>Sig. + http://repo1.maven.org/maven2/org/apache/torque/village/3.3.1/village-3.3.1-source.jar.md5";>MD5 + http://www.apache.org/dyn/closer.cgi/db/torque/torque-3.3/source/maven-torque-plugin-3.3-src.tar.gz";>TAR http://www.apache.org/dist/db/torque/torque-3.3/source/maven-torque-plugin-3.3-src.tar.gz.asc";>Sig. http://www.apache.org/dist/db/torque/torque-3.3/source/maven-torque-plugin-3.3-src.tar.gz.md5";>MD5 @@ -184,6 +200,8 @@ The currently released versions of Torqu + + http://www.apache.org/dyn/closer.cgi/db/torque/torque-3.2/source/maven-torque-plugin-3.2-src.tar.gz";>TAR http://www.apache.org/dist/db/torque/torque-3.2/source/maven-torque-plugin-3.2-src.tar.gz.asc";>Sig. http://www.apache.org/dist/db/torque/torque-3.2/source/maven-torque-plugin-3.2-src.tar.gz.md5";>MD5 @@ -200,6 +218,8 @@ The currently released versions of Torqu + + http://www.apache.org/dyn/closer.cgi/db/torque/torque-3.2/source/maven-torque-plugin-3.2-src.zip";>ZIP http://www.apache.org/dist/db/torque/torque-3.2/source/maven-torque-plugin-3.2-src.zip.asc";>Sig. http://www.apache.org/dist/db/torque/torque-3.2/source/maven-torque-plugin-3.2-src.zip.md5";>MD5 Modified: db/torque/site/trunk/xdocs/index.xml URL: http://svn.apache.org/viewvc/db/torque/site/trunk/xdocs/index.xml?rev=1078550&r1=1078549&r2=1078550&view=diff == --- db/torque/site/trunk/xdocs/index.xml (original) +++ db/torque/site/trunk/xdocs/index.xml Sun Mar 6 19:46:13 2011 @@ -118,6 +118,9 @@ Most recent production release of Torque is Torque 3.3 + +Most recent production release of the Village component of Torque is Village 3.3.1 + Modified: db/torque/site/trunk/xdocs/status.xml URL: http://svn.apache.org/viewvc/db/torque/site/trunk/xdocs/status.xml?rev=1078550&r1=1078549&r2=1078550&view=diff == --- db/torque/site/trunk/xdocs/status.xml (original) +++ db/torque/site/trunk/xdocs/status.xml Sun Mar 6 19:46:13 2011 @@ -37,6 +37,34 @@ Torque. + + +
[jira] Closed: (TORQUE-123) Statement is left open when Exception is thrown in the QueryDataSet constructor (ORA-01000)
[
https://issues.apache.org/jira/browse/TORQUE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Vandahl closed TORQUE-123.
-
Fixed in village-3.3.1
> Statement is left open when Exception is thrown in the QueryDataSet
> constructor (ORA-01000)
> -
>
> Key: TORQUE-123
> URL: https://issues.apache.org/jira/browse/TORQUE-123
> Project: Torque
> Issue Type: Bug
> Components: Village
>Affects Versions: 3.3
> Environment: OS ：RedHat Enterprise Linux ES 4 update 4
> Java ：1.4.2_08
> Tomcat：4.1.31
> Torque：3.0.2
> JDBC(Oracle): ojdbc.jar(10.2.0.4)
>Reporter: Kazu Nambo
>Assignee: Thomas Fox
> Fix For: 3.3.1
>
>
> When syntax error(SQLException) happens at executeQuery in the constructor
> QueryDataSet(Connection conn, String selectStmt), the member stmt is left
> open and this problem sometimes results in ORA-01000 (Maximum open cursors
> exceeded).
> In the upper layer like BasePeer#executeQuery method, it tries to close
> QueryDataSet instance by VillageUtils.close but it fails because the instance
> is null.
> Other exceptions may result in the same situation.
> If I try to make the constructor more robust as follows, it will work. (No
> ORA-01000)
> public QueryDataSet(Connection conn, String selectStmt)
> throws SQLException, DataSetException
> {
> this.conn = conn;
> selectString = new StringBuffer(selectStmt);
> try
> {
> stmt = conn.createStatement();
> resultSet = stmt.executeQuery(selectStmt);
> schema = new Schema();
> schema.populate(resultSet.getMetaData(), null);
> }
> catch (Exception e)
> {
> try {
> if (null != resultSet) {
> resultSet.close();
> }
> } catch (Exception ignored) {}
> try {
> if (null != stmt) {
> stmt.close();
> }
> } catch (Exception ignored) {}
> if (e instanceof SQLException)
> throw (SQLException)e;
> else if (e instanceof DataSetException)
> throw (DataSetException)e;
> else
> throw new SQLException("QueryDataSet: exception
> caught.", e);
> }
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org
For additional commands, e-mail: torque-dev-h...@db.apache.org
[jira] Updated: (TORQUE-149) If silentDbFetch is false, the add method for a related object has a throws clause
[
https://issues.apache.org/jira/browse/TORQUE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Vandahl updated TORQUE-149:
--
Fix Version/s: (was: 3.3.1)
4.0
Move fix to version 4.0
> If silentDbFetch is false, the add method for a related object has a throws
> clause
> --
>
> Key: TORQUE-149
> URL: https://issues.apache.org/jira/browse/TORQUE-149
> Project: Torque
> Issue Type: Bug
>Reporter: Thomas Fox
>Assignee: Thomas Fox
> Fix For: 4.0
>
>
> If the option torque.om.silentDbFetch is false (which is NOT the default
> value), then Torque generates from the schema
>
>
>
>
>
>
> the following code in BaseAuthor:
> public void addBook(Book l) throws TorqueException
> {
> getBooks().add(l);
> l.setAuthor((Author) this);
> }
> The throws clause is unnecessary because no Torque exception is created in
> the associated code. Thus the throws clause should be removed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org
For additional commands, e-mail: torque-dev-h...@db.apache.org
[jira] Closed: (TORQUE-36) Select performance problem with Sybase
[ https://issues.apache.org/jira/browse/TORQUE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl closed TORQUE-36. Fixed in village-3.3.1 > Select performance problem with Sybase > -- > > Key: TORQUE-36 > URL: https://issues.apache.org/jira/browse/TORQUE-36 > Project: Torque > Issue Type: Bug > Components: Runtime, Village >Affects Versions: 3.2 > Environment: Java 1.4.2 on solaris 10 against Sybase 12.5.2 >Reporter: Joe Carter >Assignee: Thomas Vandahl > Fix For: 3.3.1 > > > Selects via Torque perform 2-3 times slower than when doing the identical > statement via JDBC. > I took the SQL produced by Torque using p6spy to capture it. > I manually implemented the same SQL as a raw query and a prepared statement > obtaining a SQL connection from Torque.getConnection() to eliminate any > differences in the pooling etc. > I then ran performance tests against the 3 types. > The ratio in performance (big is slower) was 10-4-3 for standard Torque, raw > and then prepared statements. > The performance hit was definately against the database as we're seeing > similar performance improvements > on production systems with the database CPU usage dropping dramatically with > some gains on the calling tomcat server. > The suspicion is that metadata is being retrieved on every select but p6spy > unfortunately does not > support the reporting of this so this cannot be confirmed. > Note that the tests were performed without p6spy in the loop. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org For additional commands, e-mail: torque-dev-h...@db.apache.org
[jira] Closed: (TORQUE-8) village does not close every resultSet it opens
[ https://issues.apache.org/jira/browse/TORQUE-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Vandahl closed TORQUE-8. --- Fixed in village-3.3.1 > village does not close every resultSet it opens > > > Key: TORQUE-8 > URL: https://issues.apache.org/jira/browse/TORQUE-8 > Project: Torque > Issue Type: Bug > Components: Runtime, Village >Affects Versions: 3.0, 3.1, 3.1.1, 3.2 >Reporter: Thomas Fox >Assignee: Thomas Vandahl > Fix For: 3.3.1 > > Attachments: village-2.0-TORQUE-8.patch, village-3.3-TORQUE-8.patch > > > In the village classes Record and Schema, ResultSets are opened which are not > closed afterwards. This can lead to a "too many open cursors" error in > oracle. Thanks to Hendrik Busch for reporting the error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org For additional commands, e-mail: torque-dev-h...@db.apache.org
[jira] Closed: (TORQUE-154) A BLOB with NULL as its value causes a Null Pointer Exception
[
https://issues.apache.org/jira/browse/TORQUE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Vandahl closed TORQUE-154.
-
The patch is contained in village-3.3.1
> A BLOB with NULL as its value causes a Null Pointer Exception
> -
>
> Key: TORQUE-154
> URL: https://issues.apache.org/jira/browse/TORQUE-154
> Project: Torque
> Issue Type: Bug
> Components: Village
>Affects Versions: 3.3
> Environment: windows, mssql 2005
>Reporter: Rich Diaz
>Priority: Critical
> Fix For: 3.3
>
> Attachments: npe-null-blob.patch
>
>
> NPE was thrown while running the datadump task on MSSQL database. It first
> happened on Torque-gen 3.1 which has village-2.0.jar, so I took the
> village-3.3.jar from torque-gen-3.3.
> I did a search and found this link
> http://mail-archives.apache.org/mod_mbox/turbine-user/200401.mbox/%3c373ec11e4993df4f9dcbd2e630568ce31f8...@xch-au-20.au.nos.boeing.com%3E
> Looks like someone found that out in 2004.
> For village 3.3 the NPE is in Value.java line 153. I checked out the village
> source from svn, put a null check and I was able to get my datadump working.
> It's a simple null check fix. I don't see where to attach a file to this
> ticket so i'll just post the code here.
> if(blob!=null){
> valueObject = blob.getBytes(1, (int) blob.length());
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org
For additional commands, e-mail: torque-dev-h...@db.apache.org
