[Hibernate-JIRA] Created: (HHH-5185) Columns in Formulas not always rewritten, triggers ambiguous column SQL error
by Chris Wilson (JIRA)
Columns in Formulas not always rewritten, triggers ambiguous column SQL error
-----------------------------------------------------------------------------
Key: HHH-5185
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5185
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.1
Environment: MySQL Server version: 5.0.51a-3ubuntu5.5 (Ubuntu)
Hibernate version 3.5.1-Final
Reporter: Chris Wilson
Attachments: HibernateJoinFormulaAliasTest.java
The attached test case joins an entity with two @Formulas twice. The first @Formula is the algebraic expression "(kittens * 4) + 3", the second is a SQL function "EXTRACT(MONTH FROM birthday)".
kittens is rewritten but birthday is not. Because the table is joined twice, MySQL reports the error:
{code}
com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Column 'birthday' in field list is ambiguous
{code}
which shows up as:
{code}
org.hibernate.exception.ConstraintViolationException: could not load an entity: [org.aptivate.hibernate.test.HibernateJoinFormulaAliasTest$House#1]
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:96)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
at org.hibernate.loader.Loader.loadEntity(Loader.java:1937)
at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:86)
at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:76)
at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3270)
at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:496)
at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:477)
at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:227)
at org.hibernate.event.def.DefaultLoadEventListener.lockAndLoad(DefaultLoadEventListener.java:403)
at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:155)
at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:1080)
at org.hibernate.impl.SessionImpl.get(SessionImpl.java:1065)
at org.hibernate.impl.SessionImpl.get(SessionImpl.java:1056)
at org.aptivate.hibernate.test.HibernateJoinFormulaAliasTest.testFailing(HibernateJoinFormulaAliasTest.java:97)
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:597)
at org.aptivate.hibernate.test.base.HibernateTestBase.runTestMethod(HibernateTestBase.java:204)
at org.aptivate.hibernate.test.base.HibernateTestBase.runTest(HibernateTestBase.java:117)
at junit.framework.TestCase.runBare(TestCase.java:130)
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:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
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.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Column 'birthday' in field list is ambiguous
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:409)
at com.mysql.jdbc.Util.getInstance(Util.java:384)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1041)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3562)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3494)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1960)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2114)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2696)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2105)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2264)
at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208)
at org.hibernate.loader.Loader.getResultSet(Loader.java:1849)
at org.hibernate.loader.Loader.doQuery(Loader.java:718)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:270)
at org.hibernate.loader.Loader.loadEntity(Loader.java:1933)
... 31 more
{code}
The rewritten SQL is:
{code}
select
hibernatej0_.id as id0_2_,
cats1x1_.firstHome_id as firstHome4_0_4_,
cats1x1_.id as id4_,
cats1x1_.id as id1_0_,
cats1x1_.birthday as birthday1_0_,
cats1x1_.firstHome_id as firstHome4_1_0_,
cats1x1_.kittens as kittens1_0_,
cats1x1_.secondHome_id as secondHome5_1_0_,
EXTRACT(MONTH
FROM
birthday) as formula0_0_,
(cats1x1_.kittens * 4) + 3 as formula1_0_,
cats2x2_.secondHome_id as secondHome5_0_5_,
cats2x2_.id as id5_,
cats2x2_.id as id1_1_,
cats2x2_.birthday as birthday1_1_,
cats2x2_.firstHome_id as firstHome4_1_1_,
cats2x2_.kittens as kittens1_1_,
cats2x2_.secondHome_id as secondHome5_1_1_,
EXTRACT(MONTH
FROM
birthday) as formula0_1_,
(cats2x2_.kittens * 4) + 3 as formula1_1_
from
houses hibernatej0_
left outer join
cats cats1x1_
on hibernatej0_.id=cats1x1_.firstHome_id
left outer join
cats cats2x2_
on hibernatej0_.id=cats2x2_.secondHome_id
where
hibernatej0_.id=?
{code}
There's no apparent workaround that lets us reference the same column in a formula in a table that's joined twice.
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[Hibernate-JIRA] Created: (HHH-2339) merge instumented class fails
by Alexey Romanchuk (JIRA)
merge instumented class fails
-----------------------------
Key: HHH-2339
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2339
Project: Hibernate3
Type: Bug
Components: core
Versions: 3.2.1, 3.2.0.ga
Environment: Hibernate 3.2.1 (tested with 3.2.0 too)
Postgresql 8.1.4
Reporter: Alexey Romanchuk
Priority: Blocker
When we try to merge instrumented detached entity with lazy no-proxy many-to-one association we have org.hibernate.LazyInitializationException.
It occurs because cascade try to process all associations in Cascade class, but object disconected from session and can not obtaion lazy property.
If classes are not instrumented all works ok.
Why merge action does not have overrided performOnLazyProperty mathod to prevent fetching lazy properties?
Here it is small example that illustates problem.
===MAPPING===
<hibernate-mapping>
<class name="Client" table="test_client">
<id name="id" column="id" type="long">
<generator class="sequence">
<param name="sequence">test_seq</param>
</generator>
</id>
<property name="name" column="name"/>
<many-to-one name="info" class="LoginInfo" lazy="no-proxy" column="info_id" cascade="merge,evict"/>
</class>
<class name="LoginInfo" table="test_login_info">
<id name="id" column="id" type="long">
<generator class="sequence">
<param name="sequence">test_seq</param>
</generator>
</id>
<property name="login" column="login"/>
<property name="pass" column="pass"/>
</class>
</hibernate-mapping>
===JAVA===
===DOMAIN===
public class Client
{
private long id;
private String name;
private LoginInfo info;
//getters and setters
}
public class LoginInfo
{
private long id;
private String login;
private String pass;
//getters and setters
}
===USAGE===
public class Main
{
public static void main( String[] args )
{
Session s1 = sf.openSession();
s1.beginTransaction();
Client c = ( Client ) s1.get( Client.class, 2l );
s1.flush();
s1.getTransaction().commit();
s1.close();
Session s2 = sf.openSession();
s2.beginTransaction();
c = ( Client ) s2.merge( c );
s2.flush();
s2.getTransaction().commit();
s2.close();
}
}
==STACKTRACE===
org.hibernate.LazyInitializationException: session is not connected
at org.hibernate.intercept.AbstractFieldInterceptor.intercept(AbstractFieldInterceptor.java:67)
at org.hibernate.intercept.cglib.FieldInterceptorImpl.readObject(FieldInterceptorImpl.java:75)
at Client.$cglib_read_info(Client.java)
at Client.getInfo(Client.java:12)
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 org.hibernate.property.BasicPropertyAccessor$BasicGetter.get(BasicPropertyAccessor.java:145)
at org.hibernate.tuple.entity.AbstractEntityTuplizer.getPropertyValue(AbstractEntityTuplizer.java:277)
at org.hibernate.persister.entity.AbstractEntityPersister.getPropertyValue(AbstractEntityPersister.java:3529)
at org.hibernate.engine.Cascade.cascade(Cascade.java:130)
at org.hibernate.event.def.DefaultMergeEventListener.cascadeOnMerge(DefaultMergeEventListener.java:407)
at org.hibernate.event.def.DefaultMergeEventListener.entityIsDetached(DefaultMergeEventListener.java:266)
at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:120)
at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:53)
at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:677)
at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:661)
at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:665)
at Main.main(Main.java:56)
--
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
15 years, 9 months
[Hibernate-JIRA] Created: (HHH-5305) selecting elements from a collection of elements fails strangely
by Karsten Behrmann (JIRA)
selecting elements from a collection of elements fails strangely
----------------------------------------------------------------
Key: HHH-5305
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5305
Project: Hibernate Core
Issue Type: Improvement
Components: query-hql
Affects Versions: 3.5.1
Environment: PostgreSQL / hsqldb
Reporter: Karsten Behrmann
The query
"select el from Foo f join f.elements el"
produces a SQL select clause for merely "elements.id" (though joined correctly),
if "elements" is a set of composite-element.
It should rather select for all properties of the composite-element.
Effect:
- If there is no column called "id", the query fails database parse
(provoke by explicitly doing <key column="fooID" />)
- If the composite-element has more than one property, hibernate ResultSet parsing fails asking for missing col_0_1_
- If the composite-element has one property, assignment-compatible with whatever the database column "id" happens to be, the query succeeds, returning a list of elements with the property set to the value of "id".
So it seems like support is almost there. This may be a regression, or a not-quite-completed feature. Succeeding quietly with bad data is Not Good, but the case should not occur much in practice (composite-element with one property is not very useful).
Workaround: explicitly select each property, as in
"select el.name, el.created, el.importance from Foo f join f.elements el"
and manually instantiate the element class.
(This seems to still fail on <any> properties, but that is probably an unrelated problem)
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[Hibernate-JIRA] Commented: (HHH-1113) idbag composite-element cascade-on-save gives "could not bind value POST_INSERT_INDICATOR to" collection-id
by Brian Leathem (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1113?page=c... ]
Brian Leathem commented on HHH-1113:
------------------------------------
I was about to file this same bug, but found this issue in a search. I don't see anywhere in the documentation that this is a limitation. I do see a documented limitation for the idbag generator strategy "native", but not for the "identity" strategy used here. Can this bug be re-opened? Or maybe the documentation should be corrected?
> idbag composite-element cascade-on-save gives "could not bind value POST_INSERT_INDICATOR to" collection-id
> -----------------------------------------------------------------------------------------------------------
>
> Key: HHH-1113
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1113
> Project: Hibernate Core
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.5, 3.1 rc 1, 3.1 rc2
> Environment: MySQL any, MSSQL any
> Reporter: Tea Yu
> Priority: Blocker
>
> - Parent contains a List of composite-element childs (idbag)
> - the collection is cascade on all-delete-orphan
> - when saving a parent, child couldn't be persisted due to "could not bind value 'POST_INSERT_INDICATOR' to parameter", which is supposed to be generated in DB
> ------------------
> mapping
> ------------------
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE hibernate-mapping PUBLIC
> "-//Hibernate/Hibernate Mapping DTD 3.0//EN"
> "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
> <hibernate-mapping>
> <class name="Parent" table="parent">
> <id name="id" column="parent_id" type="long" unsaved-value="0">
> <generator class="native" />
> </id>
> <idbag name="childs" table="childs" cascade="all-delete-orphan">
> <collection-id column="child_id" type="long">
> <generator class="identity">
> <param name="unsaved-value">0</param>
> </generator>
> </collection-id>
> <key column="_parent_id" />
> <composite-element class="Child">
> <property name="name" column="name" type="string" />
> </composite-element>
> </idbag>
> </class>
> </hibernate-mapping>
> ------------------
> stack trace
> ------------------
> 31/10/2005 17:16:20 - DEBUG [main] (AbstractBatcher.java:344) - insert into childs (_parent_id, child_id, name) values (?, ?, ?)
> 31/10/2005 17:16:20 - DEBUG [main] (AbstractBatcher.java:413) - preparing statement
> 31/10/2005 17:16:20 - DEBUG [main] (NullableType.java:79) - binding '14' to parameter: 1
> 31/10/2005 17:16:20 - DEBUG [main] (NullableType.java:79) - binding 'POST_INSERT_INDICATOR' to parameter: 2
> 31/10/2005 17:16:20 - INFO [main] (NullableType.java:89) - could not bind value 'POST_INSERT_INDICATOR' to parameter: 2
> 31/10/2005 17:16:20 - DEBUG [main] (NullableType.java:79) - binding 'test' to parameter: 3
> 31/10/2005 17:16:20 - DEBUG [main] (BatchingBatcher.java:28) - Adding to batch
> 31/10/2005 17:16:20 - DEBUG [main] (AbstractCollectionPersister.java:1045) - done inserting collection: 1 rows inserted
> 31/10/2005 17:16:20 - DEBUG [main] (BatchingBatcher.java:55) - Executing batch size: 1
> 31/10/2005 17:16:20 - DEBUG [main] (AbstractBatcher.java:317) - about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
> 31/10/2005 17:16:20 - DEBUG [main] (AbstractBatcher.java:459) - closing statement
> 31/10/2005 17:16:20 - DEBUG [main] (JDBCExceptionReporter.java:63) - Could not execute JDBC batch update [insert into childs (_parent_id, child_id, name) values (?, ?, ?)]
> java.sql.BatchUpdateException: Statement parameter 2 not set.
> at com.mysql.jdbc.ServerPreparedStatement.executeBatch(ServerPreparedStatement.java:828)
> at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:58)
> at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:193)
> at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:230)
> at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:144)
> at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:296)
> at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
> at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:905)
> at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:345)
> at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106)
> at test.Test.testInsert(Test.java:27)
> at test.Test.main(Test.java:15)
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[Hibernate-JIRA] Created: (HHH-2388) Insert w/ identity column fails on Sybase but no exception occurs
by Tim Morrow (JIRA)
Insert w/ identity column fails on Sybase but no exception occurs
-----------------------------------------------------------------
Key: HHH-2388
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2388
Project: Hibernate3
Type: Bug
Components: core
Versions: 3.2.1
Environment: Hibernate 3.2.1.GA with annotations
Sybase jConnect 6.05 JDBC driver
Sybase ASE 15 database
Reporter: Tim Morrow
I have a scenario where storing a new entity fails (i.e. the row is not inserted) but Hibernate does not realize this. No exceptions are thrown. Later, this leads to AssertionFailures (if two such entities fail in the same session - they both have the same PK).
The problem specifically occurs with a table that has a numeric column with precision (e.g. numeric(10,4)) and an identity column when using Sybase ASE.
==========
To reproduce:
1. Use Sybase jConnect 6.05 JDBC driver with Sybase ASE 15 database.
2. Define an Entity with a long ID and BigDecimal numeric column.
3. Create a corresponding table with an identity column and numeric(10, 4) column.
For example:
hibernate.MyEntity.java:
-----------------------------------------
package hibernate;
import java.math.BigDecimal;
import javax.persistence.Column;
import javax.persistence.Entity;
import javax.persistence.GeneratedValue;
import javax.persistence.GenerationType;
import javax.persistence.Id;
import javax.persistence.Table;
import org.hibernate.validator.NotNull;
@Entity
@Table(name = "z_tim_test")
public class MyEntity {
private BigDecimal cost;
private long id;
public MyEntity() {}
@Column(columnDefinition = "numeric(10,4)")
@NotNull public final BigDecimal getCost() {
return cost;
}
@GeneratedValue(strategy = GenerationType.AUTO)
@Id public final long getId() {
return id;
}
public final void setCost(BigDecimal cost) {
this.cost = cost;
}
public final void setId(long id) {
this.id = id;
}
}
Table:
-----------------------------------------
CREATE TABLE z_tim_test
(
id numeric(19) PRIMARY KEY not null,
cost numeric(10,4) not null
);
4. Write some code that stores a new entity and tries to load it:
MyEntity myEntity = new MyEntity();
myEntity.setCost(new BigDecimal("123.12345"));
session.save(myEntity);
session.flush();
session.clear();
List<MyEntity> results = session.createCriteria(MyEntity.class).list();
if (results.size() != 1) {
throw new IllegalStateException("Expected 1 result");
}
This test will throw the IllegalStateException because the row was not persisted and no errors occurred.
Reason:
* Sybase does not thrown any SQLException when you try and persist a numeric value whose scale exceeds that defined on the column. Instead, it returns an updateCount of zero and an identity column value of zero.
* Hibernate does not check the updateCount after executing the statement when using an Identity column. The offending code is in:
org.hibernate.id.IdentityGenerator$InsertSelectDelegate
public Serializable executeAndExtract(PreparedStatement insert) throws SQLException {
if ( !insert.execute() ) {
while ( !insert.getMoreResults() && insert.getUpdateCount() != -1 ) {
// do nothing until we hit the rsult set containing the generated id
}
}
ResultSet rs = insert.getResultSet();
try {
return IdentifierGeneratorFactory.getGeneratedIdentity( rs, persister.getIdentifierType() );
}
finally {
rs.close();
}
}
It ignores the updateCount.
The net result is that the object is assigned a PK value of zero. Hibernate continues. My applicaiton is unaware that the row failed to insert.
Solution:
It would seem to me replacing the above code with:
if (!insert.execute()) {
if (insert.getUpdateCount() < 1) {
throw new HibernateException("No update occurred");
}
while (!insert.getMoreResults()) {
// do nothing until we hit the rsult set containing the generated id
}
}
Would take care of the problem?
--
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
15 years, 9 months
[Hibernate-JIRA] Created: (HHH-5333) Dynamically setting schema name for native queries in hbm file
by Niraj Gadgilwar (JIRA)
Dynamically setting schema name for native queries in hbm file
--------------------------------------------------------------
Key: HHH-5333
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5333
Project: Hibernate Core
Issue Type: Task
Components: query-sql
Affects Versions: 3.3.2, 3.3.0.SP1, 3.2.2
Reporter: Niraj Gadgilwar
Hi ,
inside my hibernate.cfg.xml I am mentioning
hibernate.default_schema as schema name (say "testSchema") and it is working with named queries and HQL as expected.But when I am using a native sql query
<sql-query name="myQuery">
<return-scalar column="NAME" type="java.lang.String"/>
<return-scalar column="SURNAME" type="java.lang.String"/>
SELECT NAME,SURNAME FROM ${hibernate.default_schema}.TBEMPLOYEE
</sql-query>
In that case the schema name(i.e. testSchema)is not getting appended to the table names.
I tried this for Hibernate version 3.3.0 and 3.3.2. But it is not working.
Can anybody provide me the correct implementation ? Do anyone know correct syntax?
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months