hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-450) Support for Some PostgreSQL Types (Contribution)

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-450


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-450
    Summary: Support for Some PostgreSQL Types (Contribution)
       Type: New Feature

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Jesse Costello-Good

    Created: Mon, 3 Nov 2003 11:35 AM
    Updated: Mon, 3 Nov 2003 11:35 AM

Description:
Here's some classes to support PostgreSQL circle, lseg, point, inet, string[], box, and polygon types.  It includes tests and a build.xml.  

I'm not really sure how to contribute this, so I'll post it here.  Feel free to contact me if there is some other way in which I should post this.




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] Object Relational Mapping Performance (Hibernate)

[William R. L. <wr...@ex...>]

All,

I've recently taken to exploring Hibernate <http://www.hibernate.org/> for
use in Object Relational Mapping, and it seems overall to be quite the
excellent package.  I understand that the Apache Foundation also offers
their OJB packages that will help to accomplish a similar end result, and
I'm sure there's others that people might suggest (comments welcome!).

This stuff is all good, and I've found that ORM tools do in fact help to
decrease development time requirements; however, I've noticed that in
using these tools, there seems to be quite a bit more overhead involved in
accessing databased information.  Hibernate itself doesn't support raw
INNER JOINS for example, and this requires that all object relations are
defined in the Hibernate object mapping configurations.  Additionally, I'm
finding that if I have an Object containing child objects within a Set
(think one-to-many mappings), and if I want to retrieve just a subset of
those children based on query criteria, the parent Object must still be
populated with all its children if it is to be loaded, accessed, modified,
and later saved again as a persistent Object (this might be needed if more
children are added to the Set, for example).  This of course creates quite
the burden on resources when working with somewhat larger databases.

One could of course throw more hardware at the problem to improve
application performance, but I don't find this to be an acceptable
solution for robust applications.  And so, I'd like to ask if others have
encountered this same plight and found a method to improve performance?  
Do people just not use ORM for database-intensive Java applications?

Any and all suggestions are welcome; I'm eager to learn what I can.

Thanks, in advance, for any thoughts on this.

--          _ 
__ __ ___ _| | William R. Lorenz <wr...@ex...> 
\ V  V / '_| | http://www.clevelandlug.net/ ; "Every revolution was 
 \./\./|_| |_| first a thought in one man's mind." - Ralph Waldo Emerson 

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-158) Customizable SQL

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Michail Jekimov
    Created: Mon, 3 Nov 2003 9:08 AM
       Body:
Hello,

I tried to implement the discussed functionality. Here is the result as a patch. Unfortunately I had problems with cvs connection to the sourceforge host. So, this is the diff patch for Hibernate 2.1 beta 4. Surely I cannot guarantee that these changes won't produce any side effects, but I hope it will help you if you decide to implement this feature.

--- SelectParser_old.java       Mon Nov  3 15:59:06 2003
+++ SelectParser.java   Mon Nov  3 15:59:06 2003
@@ -35,6 +35,7 @@
        private boolean first;
        private boolean afterNew;
        private boolean insideNew;
+       private boolean aggregateAddSelectScalar;
        private Class holderClass;

        private final SelectPathExpressionParser pathExpressionParser;
@@ -71,7 +72,7 @@
                        insideNew = true;
                }
                else if ( token.equals(StringHelper.COMMA) ) {
-                       if (ready) throw new QueryException("alias or expression expected in SELECT");
+                       if (!aggregate && ready) throw new QueryException("alias or expression expected in SELECT");
                        q.appendScalarSelectToken(StringHelper.COMMA_SPACE);
                        ready=true;
                }
@@ -118,6 +119,7 @@
                        // the name of an SQL function
                        if (!ready) throw new QueryException(", expected before aggregate function in SELECT: " + token);
                        aggregate = true;
+                       aggregateAddSelectScalar = true;
                        aggregateFuncTokenList.add(lctoken);
                        ready = false;
                        q.appendScalarSelectToken(token);
@@ -136,18 +138,31 @@
                        }
                }
                else if (aggregate) {
+                       boolean constantToken = false;
                        if (!ready) throw new QueryException("( expected after aggregate function in SELECT");
+                       try {
                        ParserHelper.parse(aggregatePathExpressionParser, q.unalias(token), ParserHelper.PATH_SEPARATORS, q);
+                       } catch (QueryException qex) {
+                               constantToken = true;
+                       }

-                       if ( aggregatePathExpressionParser.isCollectionValued() ) {
-                               q.addCollection(
-                                       aggregatePathExpressionParser.getCollectionName(),
-                                       aggregatePathExpressionParser.getCollectionRole()
-                               );
-                       }
-                       q.appendScalarSelectToken( aggregatePathExpressionParser.getWhereColumn() );
-                       q.addSelectScalar( aggregateType(aggregateFuncTokenList, aggregatePathExpressionParser.getWhereColumnType(), q ) );
-                       aggregatePathExpressionParser.addAssociation(q);
+                       if (constantToken) {
+                               q.appendScalarSelectToken(token);
+                       }
+                       else {
+                               if ( aggregatePathExpressionParser.isCollectionValued() ) {
+                                       q.addCollection(
+                                               aggregatePathExpressionParser.getCollectionName(),
+                                               aggregatePathExpressionParser.getCollectionRole()
+                                       );
+                               }
+                               q.appendScalarSelectToken( aggregatePathExpressionParser.getWhereColumn() );
+                               if (aggregateAddSelectScalar) {
+                                       q.addSelectScalar( aggregateType(aggregateFuncTokenList, aggregatePathExpressionParser.getWhereColumnType(), q ) );
+                                       aggregateAddSelectScalar = false;
+                               }
+                               aggregatePathExpressionParser.addAssociation(q);
+                       }
                }
                else {
                        if (!ready) throw new QueryException(", expected in SELECT");

=====================================================================

--- QueryTranslator_old.java    Mon Nov  3 15:59:06 2003
+++ QueryTranslator.java        Mon Nov  3 15:59:06 2003
@@ -654,6 +654,12 @@
                                Object next = iter.next();
                                if (next instanceof String) {
                                        String token = (String) next;
+                                       if (StringHelper.OPEN_PAREN.equals(token)) {
+                                               isSubselect = true;
+                                       }
+                                       else if (StringHelper.CLOSE_PAREN.equals(token)) {
+                                               isSubselect = superQuery!=null;
+                                       }
                                        String lc = token.toLowerCase();
                                        if ( lc.equals(StringHelper.COMMA_SPACE) ) {
                                                if (nolast) {

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-158


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-158
    Summary: Customizable SQL
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:38 PM
    Updated: Tue, 8 Jul 2003 3:38 PM

Description:
Ability to be able to get the SQL Hibernate would send to the database for a given query,
be able to look at it and possibly tweak it (as a String) and then allow Hibernate to
continue - sending the SQL on its way to the database.  This allows for subtle hints and
other database tricks one is often forced to do when you don't "own" the datamodel.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-449) ScrollableResults setRowNumber()

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Martin Priekopa
    Created: Mon, 3 Nov 2003 8:34 AM
       Body:
;) sorry this one counts.

public boolean setRowNumber(int rowNumber) throws HibernateException {
if (rowNumber>=0) rowNumber++;
try {
return rs.absolute(rowNumber);
}
catch (SQLException sqle) {
throw new JDBCException(sqle);
}
}

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-449


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-449
    Summary: ScrollableResults setRowNumber()
       Type: Patch

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Martin Priekopa

    Created: Mon, 3 Nov 2003 8:10 AM
    Updated: Mon, 3 Nov 2003 8:10 AM

Description:
I think that implementation of ScrollableResultsImpl method:
public boolean setRowNumber(int rowNumber) throws HibernateException {
	if (rowNumber>0) rowNumber--;
	try {
		return rs.absolute(rowNumber);
	}
	catch (SQLException sqle) {
		throw new JDBCException(sqle);
	}
}

should IMHO look like this one:
public boolean setRowNumber(int rowNumber) throws HibernateException {
	if (rowNumber>0) rowNumber++;
	try {
		return rs.absolute(rowNumber);
	}
	catch (SQLException sqle) {
		throw new JDBCException(sqle);
	}
}

Or if you want to be java.sql.ResultSet compatible, both setRowNumber and getRowNumber should be wrappers only.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-449) ScrollableResults setRowNumber()

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-449


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-449
    Summary: ScrollableResults setRowNumber()
       Type: Patch

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Martin Priekopa

    Created: Mon, 3 Nov 2003 8:10 AM
    Updated: Mon, 3 Nov 2003 8:10 AM

Description:
I think that implementation of ScrollableResultsImpl method:
public boolean setRowNumber(int rowNumber) throws HibernateException {
	if (rowNumber>0) rowNumber--;
	try {
		return rs.absolute(rowNumber);
	}
	catch (SQLException sqle) {
		throw new JDBCException(sqle);
	}
}

should IMHO look like this one:
public boolean setRowNumber(int rowNumber) throws HibernateException {
	if (rowNumber>0) rowNumber++;
	try {
		return rs.absolute(rowNumber);
	}
	catch (SQLException sqle) {
		throw new JDBCException(sqle);
	}
}

Or if you want to be java.sql.ResultSet compatible, both setRowNumber and getRowNumber should be wrappers only.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-158) Customizable SQL

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Mon, 3 Nov 2003 4:23 AM
       Body:
so - should we throw this at David ? (he talked about doing this in Aarhus)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-158


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-158
    Summary: Customizable SQL
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:38 PM
    Updated: Tue, 8 Jul 2003 3:38 PM

Description:
Ability to be able to get the SQL Hibernate would send to the database for a given query,
be able to look at it and possibly tweak it (as a String) and then allow Hibernate to
continue - sending the SQL on its way to the database.  This allows for subtle hints and
other database tricks one is often forced to do when you don't "own" the datamodel.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-440) Direct collection property access

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Mon, 3 Nov 2003 4:22 AM
       Body:
yup (unless you can fix it in 5 ;)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-440


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-440
    Summary: Direct collection property access 
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: Max Rydahl Andersen
   Reporter: Alexey Kaigorodov

    Created: Fri, 31 Oct 2003 3:26 AM
    Updated: Mon, 3 Nov 2003 2:52 AM

Description:
<bag name="..." access="field">
 ...
</bag>

causes exception unless exists getter

net.sf.hibernate.MappingException: Problem trying to set property type by reflection
	at net.sf.hibernate.mapping.Value.setTypeByReflection(Value.java:103)
	at net.sf.hibernate.cfg.Binder.createProperty(Binder.java:953)
	at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:946)
	at net.sf.hibernate.cfg.Binder.bindRootClass(Binder.java:313)
	at net.sf.hibernate.cfg.Binder.bindRoot(Binder.java:1143)
	at net.sf.hibernate.cfg.Configuration.add(Configuration.java:243)
	at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:266)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:349)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:320)
      ...
Caused by: net.sf.hibernate.PropertyNotFoundException: Could not find a getter for ... in class ...

--
With best regards,
Alexey


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-448) SchemaExport: Unique constraint names too long for DB/2

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Mon, 3 Nov 2003 4:19 AM

Fixed in CVS
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-448


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-448
    Summary: SchemaExport: Unique constraint names too long for DB/2
       Type: Bug

     Status: Closed
   Priority: Critical
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 rc1
   Versions:
             2.1 beta 4

   Assignee: 
   Reporter: Jan Riis

    Created: Mon, 3 Nov 2003 3:51 AM
    Updated: Mon, 3 Nov 2003 4:19 AM
Environment: Win Xp prof., DB2 7.2, JDK-1.4.2

Description:
When generating schema for *subclasses* having <many-to-one ... /> associations, the generated constraint-name exeeds 18 characters when using DB/2 dialect.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-158) Customizable SQL

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gavin King
    Created: Mon, 3 Nov 2003 4:19 AM
       Body:
It does not yet support multiple arguments.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-158


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-158
    Summary: Customizable SQL
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:38 PM
    Updated: Tue, 8 Jul 2003 3:38 PM

Description:
Ability to be able to get the SQL Hibernate would send to the database for a given query,
be able to look at it and possibly tweak it (as a String) and then allow Hibernate to
continue - sending the SQL on its way to the database.  This allows for subtle hints and
other database tricks one is often forced to do when you don't "own" the datamodel.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-158) Customizable SQL

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Michail Jekimov
    Created: Mon, 3 Nov 2003 4:12 AM
       Body:
Hello Gavin,

I tried to register my PL/SQL function by subclassing the OracleDialect in the following way:

public class MyDatabaseDialect extends OracleDialect {

	public MyDatabaseDialect() {
		super();
		registerFunction("get_price", new SQLFunction() {

			public Type getReturnType(Type columnType, Mapping mapping) {
				return Hibernate.INTEGER;
			}

			public boolean hasArguments() {
				return true;
			}

			public boolean hasParenthesesIfNoArguments() {
				return true;
			}

		});
	}
}

When I try to execute a query with this function, Hibernate throws the following:

net.sf.hibernate.QueryException: alias or expression expected in SELECT [ select min( get_price(stockItem.id, 1.0)) from StockItem stockItem  where stockItem.stock.id = ?]
	at net.sf.hibernate.hql.SelectParser.token(SelectParser.java:74)
	at net.sf.hibernate.hql.ClauseParser.token(ClauseParser.java:87)
	at net.sf.hibernate.hql.ClauseParser.end(ClauseParser.java:114)
	at net.sf.hibernate.hql.PreprocessingParser.end(PreprocessingParser.java:143)
	at net.sf.hibernate.hql.ParserHelper.parse(ParserHelper.java:30)

When I register a function that needs only one parameter everything works fine. But I really need to pass more than one parameter to it.
Is it a wrong way to define my own SQL functions?
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-158


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-158
    Summary: Customizable SQL
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:38 PM
    Updated: Tue, 8 Jul 2003 3:38 PM

Description:
Ability to be able to get the SQL Hibernate would send to the database for a given query,
be able to look at it and possibly tweak it (as a String) and then allow Hibernate to
continue - sending the SQL on its way to the database.  This allows for subtle hints and
other database tricks one is often forced to do when you don't "own" the datamodel.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-448) SchemaExport: Unique constraint names too long for DB/2

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gavin King
    Created: Mon, 3 Nov 2003 4:02 AM
       Body:
Don't worry; I reproduced.

Bad.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-448


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-448
    Summary: SchemaExport: Unique constraint names too long for DB/2
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 4

   Assignee: 
   Reporter: Jan Riis

    Created: Mon, 3 Nov 2003 3:51 AM
    Updated: Mon, 3 Nov 2003 3:51 AM
Environment: Win Xp prof., DB2 7.2, JDK-1.4.2

Description:
When generating schema for *subclasses* having <many-to-one ... /> associations, the generated constraint-name exeeds 18 characters when using DB/2 dialect.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-447) SAPDB hangs with big strings.

[<leg...@at...>]

The following comment has been added to this issue:

     Author: the_Ellessar
    Created: Mon, 3 Nov 2003 4:00 AM
       Body:
I'll subclass the sapdb dialect, seems to be the best solution.

Thnx.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-447


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-447
    Summary: SAPDB hangs with big strings.
       Type: Patch

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.2

   Assignee: 
   Reporter: the_Ellessar

    Created: Mon, 3 Nov 2003 2:44 AM
    Updated: Mon, 3 Nov 2003 3:04 AM
Environment: Sapdb 7.4, Linux red hat 9

Description:
I'm having a problem with SapDB and long strings. It is probably a bug in SapDB (driver) but I made an easy fix in the sapdb dialect. 

According to the SapDB documentation it is possible to put dat with a length 8k in a VARCHAR field, but when I define a string with length bigger than 1024 SapDB becomes REAL slow. 

As far as I know the clob type doesn't work very well with the SAP JDBC driver.

So I created the next patch:

Index: SAPDBDialect.java
===================================================================
RCS file: /cvsroot/hibernate/Hibernate2/src/net/sf/hibernate/dialect/SAPDBDialect.java,v
retrieving revision 1.12
diff -u -r1.12 SAPDBDialect.java
--- SAPDBDialect.java	30 Jul 2003 02:53:06 -0000	1.12
+++ SAPDBDialect.java	3 Nov 2003 08:43:48 -0000
@@ -25,7 +25,8 @@
 		register( Types.TINYINT, "FIXED(3,0)" );
 		register( Types.INTEGER, "INT" );
 		register( Types.CHAR, "CHAR(1)" );
-		register( Types.VARCHAR, "VARCHAR($l)" );
+		register( Types.VARCHAR, 512, "VARCHAR($l)" );
+		register( Types.VARCHAR, "LONG VARCHAR" );
 		register( Types.FLOAT, "FLOAT" );
 		register( Types.DOUBLE, "DOUBLE PRECISION" );
 		register( Types.DATE, "DATE" );



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-448) SchemaExport: Unique constraint names too long for DB/2

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gavin King
    Created: Mon, 3 Nov 2003 3:58 AM
       Body:
show the mapping please
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-448


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-448
    Summary: SchemaExport: Unique constraint names too long for DB/2
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 4

   Assignee: 
   Reporter: Jan Riis

    Created: Mon, 3 Nov 2003 3:51 AM
    Updated: Mon, 3 Nov 2003 3:51 AM
Environment: Win Xp prof., DB2 7.2, JDK-1.4.2

Description:
When generating schema for *subclasses* having <many-to-one ... /> associations, the generated constraint-name exeeds 18 characters when using DB/2 dialect.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-447) SAPDB hangs with big strings.

[<leg...@at...>]

The following comment has been added to this issue:

     Author: the_Ellessar
    Created: Mon, 3 Nov 2003 3:51 AM
       Body:
According to

http://www.sapdb.org/7.4/htmhelp/da/ed9036dfe4b903e10000009b38f889/frameset.htm
---
An alphanumerical column is defined. Specification of length attribute n is optional. If no other length attribute is specified, then n=1.

VARCHAR [(n)]: 0<n<=8000
VARCHAR [(n)] UNICODE: 0<n<=4000

Use VARCHAR (n) if the values in the column are to be stored with a variable length, irrespective of n.
---

But my own experience is that I have problems with strings starting around 1024. could be it's a JDBC Driver problem, I don't have the problem in the sql client.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-447


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-447
    Summary: SAPDB hangs with big strings.
       Type: Patch

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.2

   Assignee: 
   Reporter: the_Ellessar

    Created: Mon, 3 Nov 2003 2:44 AM
    Updated: Mon, 3 Nov 2003 3:04 AM
Environment: Sapdb 7.4, Linux red hat 9

Description:
I'm having a problem with SapDB and long strings. It is probably a bug in SapDB (driver) but I made an easy fix in the sapdb dialect. 

According to the SapDB documentation it is possible to put dat with a length 8k in a VARCHAR field, but when I define a string with length bigger than 1024 SapDB becomes REAL slow. 

As far as I know the clob type doesn't work very well with the SAP JDBC driver.

So I created the next patch:

Index: SAPDBDialect.java
===================================================================
RCS file: /cvsroot/hibernate/Hibernate2/src/net/sf/hibernate/dialect/SAPDBDialect.java,v
retrieving revision 1.12
diff -u -r1.12 SAPDBDialect.java
--- SAPDBDialect.java	30 Jul 2003 02:53:06 -0000	1.12
+++ SAPDBDialect.java	3 Nov 2003 08:43:48 -0000
@@ -25,7 +25,8 @@
 		register( Types.TINYINT, "FIXED(3,0)" );
 		register( Types.INTEGER, "INT" );
 		register( Types.CHAR, "CHAR(1)" );
-		register( Types.VARCHAR, "VARCHAR($l)" );
+		register( Types.VARCHAR, 512, "VARCHAR($l)" );
+		register( Types.VARCHAR, "LONG VARCHAR" );
 		register( Types.FLOAT, "FLOAT" );
 		register( Types.DOUBLE, "DOUBLE PRECISION" );
 		register( Types.DATE, "DATE" );



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-448) SchemaExport: Unique constraint names too long for DB/2

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-448


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-448
    Summary: SchemaExport: Unique constraint names too long for DB/2
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 4

   Assignee: 
   Reporter: Jan Riis

    Created: Mon, 3 Nov 2003 3:51 AM
    Updated: Mon, 3 Nov 2003 3:51 AM
Environment: Win Xp prof., DB2 7.2, JDK-1.4.2

Description:
When generating schema for *subclasses* having <many-to-one ... /> associations, the generated constraint-name exeeds 18 characters when using DB/2 dialect.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-158) Customizable SQL

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gavin King
    Created: Mon, 3 Nov 2003 3:34 AM
       Body:
Yes, it is very well-known and has a very good reason :)

Hibernate 2.1 allows you to specify Dialect-specific SQL functions, which may then be used in the SELECT clause.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-158


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-158
    Summary: Customizable SQL
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:38 PM
    Updated: Tue, 8 Jul 2003 3:38 PM

Description:
Ability to be able to get the SQL Hibernate would send to the database for a given query,
be able to look at it and possibly tweak it (as a String) and then allow Hibernate to
continue - sending the SQL on its way to the database.  This allows for subtle hints and
other database tricks one is often forced to do when you don't "own" the datamodel.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-158) Customizable SQL

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Michail Jekimov
    Created: Mon, 3 Nov 2003 3:19 AM
       Body:
An addition: it seems that I can use proprietary SQL functions in the where clause of my HQL statements but not in the select clause. Is that a known issue, and if yes, is it planned to allow using SQL functions in the select clause?

Michail.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-158


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-158
    Summary: Customizable SQL
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.1

   Assignee: 
   Reporter: TURIN ACCOUNT

    Created: Tue, 8 Jul 2003 3:38 PM
    Updated: Tue, 8 Jul 2003 3:38 PM

Description:
Ability to be able to get the SQL Hibernate would send to the database for a given query,
be able to look at it and possibly tweak it (as a String) and then allow Hibernate to
continue - sending the SQL on its way to the database.  This allows for subtle hints and
other database tricks one is often forced to do when you don't "own" the datamodel.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-447) SAPDB hangs with big strings.

[<leg...@at...>]

The following issue has been updated:

    Updater: Gavin King (mailto:ga...@hi...)
       Date: Mon, 3 Nov 2003 3:04 AM
    Changes:
             type changed from Bug
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-447&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-447


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-447
    Summary: SAPDB hangs with big strings.
       Type: Patch

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.2

   Assignee: 
   Reporter: the_Ellessar

    Created: Mon, 3 Nov 2003 2:44 AM
    Updated: Mon, 3 Nov 2003 3:04 AM
Environment: Sapdb 7.4, Linux red hat 9

Description:
I'm having a problem with SapDB and long strings. It is probably a bug in SapDB (driver) but I made an easy fix in the sapdb dialect. 

According to the SapDB documentation it is possible to put dat with a length 8k in a VARCHAR field, but when I define a string with length bigger than 1024 SapDB becomes REAL slow. 

As far as I know the clob type doesn't work very well with the SAP JDBC driver.

So I created the next patch:

Index: SAPDBDialect.java
===================================================================
RCS file: /cvsroot/hibernate/Hibernate2/src/net/sf/hibernate/dialect/SAPDBDialect.java,v
retrieving revision 1.12
diff -u -r1.12 SAPDBDialect.java
--- SAPDBDialect.java	30 Jul 2003 02:53:06 -0000	1.12
+++ SAPDBDialect.java	3 Nov 2003 08:43:48 -0000
@@ -25,7 +25,8 @@
 		register( Types.TINYINT, "FIXED(3,0)" );
 		register( Types.INTEGER, "INT" );
 		register( Types.CHAR, "CHAR(1)" );
-		register( Types.VARCHAR, "VARCHAR($l)" );
+		register( Types.VARCHAR, 512, "VARCHAR($l)" );
+		register( Types.VARCHAR, "LONG VARCHAR" );
 		register( Types.FLOAT, "FLOAT" );
 		register( Types.DOUBLE, "DOUBLE PRECISION" );
 		register( Types.DATE, "DATE" );



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-426) Enable observation of StaleObjectStateException

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gavin King
    Created: Mon, 3 Nov 2003 2:56 AM
       Body:
Would also be very good to be able to /ignore/ the failure and do the update anyway, I suppose.

http://forum.hibernate.org/viewtopic.php?p=2176688#2176688
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-426


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-426
    Summary: Enable observation of StaleObjectStateException
       Type: New Feature

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 4

   Assignee: Gavin King
   Reporter: John Kristian

    Created: Mon, 27 Oct 2003 11:46 AM
    Updated: Mon, 3 Nov 2003 2:54 AM

Description:
Please enable application software to take action whenever optimistic concurrency control fails (for example, whenever a database change fails because the version of an affected row is different from the version last read).  As I understand it, whenever Hibernate detects this it throws a StaleObjectStateException, which is helpful.  But StaleObjectStateException might propagate from any one of many Hibernate methods, which makes it difficult for an application to observe it.

I'd like one method in my application to be called whenever Hibernate throws a StaleObjectStateException.  (In my application, that method will evict stale entries from the global cache, using an algorithm that's too expensive to execute more frequently.)

A related forum thread: http://forum.hibernate.org/viewtopic.php?t=925032

The Observer pattern (from 'Design Patterns') seems applicable here.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-426) Enable observation of StaleObjectStateException

[<leg...@at...>]

Message:

   The following issue has been re-assigned.

   Assignee: Gavin King (mailto:ga...@hi...)
   Assigner: Gavin King (mailto:ga...@hi...)
       Date: Mon, 3 Nov 2003 2:54 AM
    Comment:
Assigning to me, so i don't forget
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-426


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-426
    Summary: Enable observation of StaleObjectStateException
       Type: New Feature

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 4

   Assignee: Gavin King
   Reporter: John Kristian

    Created: Mon, 27 Oct 2003 11:46 AM
    Updated: Mon, 3 Nov 2003 2:54 AM

Description:
Please enable application software to take action whenever optimistic concurrency control fails (for example, whenever a database change fails because the version of an affected row is different from the version last read).  As I understand it, whenever Hibernate detects this it throws a StaleObjectStateException, which is helpful.  But StaleObjectStateException might propagate from any one of many Hibernate methods, which makes it difficult for an application to observe it.

I'd like one method in my application to be called whenever Hibernate throws a StaleObjectStateException.  (In my application, that method will evict stale entries from the global cache, using an algorithm that's too expensive to execute more frequently.)

A related forum thread: http://forum.hibernate.org/viewtopic.php?t=925032

The Observer pattern (from 'Design Patterns') seems applicable here.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-447) SAPDB hangs with big strings.

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gavin King
    Created: Mon, 3 Nov 2003 2:53 AM
       Body:
Ah ... if you can find some kind of "official" doco or statement that there is a limited max size to SAPDB varchars, I will change ... otherwise just keep working with a customized Dialect (can't you just subclass the built-in Dialect?)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-447


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-447
    Summary: SAPDB hangs with big strings.
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.2

   Assignee: 
   Reporter: the_Ellessar

    Created: Mon, 3 Nov 2003 2:44 AM
    Updated: Mon, 3 Nov 2003 2:44 AM
Environment: Sapdb 7.4, Linux red hat 9

Description:
I'm having a problem with SapDB and long strings. It is probably a bug in SapDB (driver) but I made an easy fix in the sapdb dialect. 

According to the SapDB documentation it is possible to put dat with a length 8k in a VARCHAR field, but when I define a string with length bigger than 1024 SapDB becomes REAL slow. 

As far as I know the clob type doesn't work very well with the SAP JDBC driver.

So I created the next patch:

Index: SAPDBDialect.java
===================================================================
RCS file: /cvsroot/hibernate/Hibernate2/src/net/sf/hibernate/dialect/SAPDBDialect.java,v
retrieving revision 1.12
diff -u -r1.12 SAPDBDialect.java
--- SAPDBDialect.java	30 Jul 2003 02:53:06 -0000	1.12
+++ SAPDBDialect.java	3 Nov 2003 08:43:48 -0000
@@ -25,7 +25,8 @@
 		register( Types.TINYINT, "FIXED(3,0)" );
 		register( Types.INTEGER, "INT" );
 		register( Types.CHAR, "CHAR(1)" );
-		register( Types.VARCHAR, "VARCHAR($l)" );
+		register( Types.VARCHAR, 512, "VARCHAR($l)" );
+		register( Types.VARCHAR, "LONG VARCHAR" );
 		register( Types.FLOAT, "FLOAT" );
 		register( Types.DOUBLE, "DOUBLE PRECISION" );
 		register( Types.DATE, "DATE" );



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-440) Direct collection property access

[<leg...@at...>]

Message:

   The following issue has been re-assigned.

   Assignee: Max Rydahl Andersen (mailto:xa...@xa...)
   Assigner: Gavin King (mailto:ga...@hi...)
       Date: Mon, 3 Nov 2003 2:52 AM
    Comment:
Yours, Max?
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-440


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-440
    Summary: Direct collection property access 
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: Max Rydahl Andersen
   Reporter: Alexey Kaigorodov

    Created: Fri, 31 Oct 2003 3:26 AM
    Updated: Mon, 3 Nov 2003 2:52 AM

Description:
<bag name="..." access="field">
 ...
</bag>

causes exception unless exists getter

net.sf.hibernate.MappingException: Problem trying to set property type by reflection
	at net.sf.hibernate.mapping.Value.setTypeByReflection(Value.java:103)
	at net.sf.hibernate.cfg.Binder.createProperty(Binder.java:953)
	at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:946)
	at net.sf.hibernate.cfg.Binder.bindRootClass(Binder.java:313)
	at net.sf.hibernate.cfg.Binder.bindRoot(Binder.java:1143)
	at net.sf.hibernate.cfg.Configuration.add(Configuration.java:243)
	at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:266)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:349)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:320)
      ...
Caused by: net.sf.hibernate.PropertyNotFoundException: Could not find a getter for ... in class ...

--
With best regards,
Alexey


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-447) SAPDB hangs with big strings.

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-447


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-447
    Summary: SAPDB hangs with big strings.
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.2

   Assignee: 
   Reporter: the_Ellessar

    Created: Mon, 3 Nov 2003 2:44 AM
    Updated: Mon, 3 Nov 2003 2:44 AM
Environment: Sapdb 7.4, Linux red hat 9

Description:
I'm having a problem with SapDB and long strings. It is probably a bug in SapDB (driver) but I made an easy fix in the sapdb dialect. 

According to the SapDB documentation it is possible to put dat with a length 8k in a VARCHAR field, but when I define a string with length bigger than 1024 SapDB becomes REAL slow. 

As far as I know the clob type doesn't work very well with the SAP JDBC driver.

So I created the next patch:

Index: SAPDBDialect.java
===================================================================
RCS file: /cvsroot/hibernate/Hibernate2/src/net/sf/hibernate/dialect/SAPDBDialect.java,v
retrieving revision 1.12
diff -u -r1.12 SAPDBDialect.java
--- SAPDBDialect.java	30 Jul 2003 02:53:06 -0000	1.12
+++ SAPDBDialect.java	3 Nov 2003 08:43:48 -0000
@@ -25,7 +25,8 @@
 		register( Types.TINYINT, "FIXED(3,0)" );
 		register( Types.INTEGER, "INT" );
 		register( Types.CHAR, "CHAR(1)" );
-		register( Types.VARCHAR, "VARCHAR($l)" );
+		register( Types.VARCHAR, 512, "VARCHAR($l)" );
+		register( Types.VARCHAR, "LONG VARCHAR" );
 		register( Types.FLOAT, "FLOAT" );
 		register( Types.DOUBLE, "DOUBLE PRECISION" );
 		register( Types.DATE, "DATE" );



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-440) Direct collection property access

[<leg...@at...>]

The following issue has been updated:

    Updater: Alexey Kaigorodov (mailto:a1...@ic...)
       Date: Sun, 2 Nov 2003 9:23 PM
    Changes:
             Attachment changed to Foo.java
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-440&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-440


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-440
    Summary: Direct collection property access 
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Alexey Kaigorodov

    Created: Fri, 31 Oct 2003 3:26 AM
    Updated: Sun, 2 Nov 2003 9:23 PM

Description:
<bag name="..." access="field">
 ...
</bag>

causes exception unless exists getter

net.sf.hibernate.MappingException: Problem trying to set property type by reflection
	at net.sf.hibernate.mapping.Value.setTypeByReflection(Value.java:103)
	at net.sf.hibernate.cfg.Binder.createProperty(Binder.java:953)
	at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:946)
	at net.sf.hibernate.cfg.Binder.bindRootClass(Binder.java:313)
	at net.sf.hibernate.cfg.Binder.bindRoot(Binder.java:1143)
	at net.sf.hibernate.cfg.Configuration.add(Configuration.java:243)
	at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:266)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:349)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:320)
      ...
Caused by: net.sf.hibernate.PropertyNotFoundException: Could not find a getter for ... in class ...

--
With best regards,
Alexey


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-440) Direct collection property access

[<leg...@at...>]

The following issue has been updated:

    Updater: Alexey Kaigorodov (mailto:a1...@ic...)
       Date: Sun, 2 Nov 2003 9:23 PM
    Changes:
             Attachment changed to Foo.hbm.xml
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-440&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-440


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-440
    Summary: Direct collection property access 
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: Alexey Kaigorodov

    Created: Fri, 31 Oct 2003 3:26 AM
    Updated: Sun, 2 Nov 2003 9:23 PM

Description:
<bag name="..." access="field">
 ...
</bag>

causes exception unless exists getter

net.sf.hibernate.MappingException: Problem trying to set property type by reflection
	at net.sf.hibernate.mapping.Value.setTypeByReflection(Value.java:103)
	at net.sf.hibernate.cfg.Binder.createProperty(Binder.java:953)
	at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:946)
	at net.sf.hibernate.cfg.Binder.bindRootClass(Binder.java:313)
	at net.sf.hibernate.cfg.Binder.bindRoot(Binder.java:1143)
	at net.sf.hibernate.cfg.Configuration.add(Configuration.java:243)
	at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:266)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:349)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:320)
      ...
Caused by: net.sf.hibernate.PropertyNotFoundException: Could not find a getter for ... in class ...

--
With best regards,
Alexey


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira