November 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Resolved: (HHH-1599) ConstraintViolationException returns null with PostgresDialect (Solution included)

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1599?page=c... ] Diego Pires Plentz resolved HHH-1599. ------------------------------------- Assignee: Diego Pires Plentz Resolution: Cannot Reproduce Just tested against hibernate 3.2.5, postgre 8.2, postgresql-8.2-506.jdbc4.jar Hibernate: insert into testfoo (test_foo, id) values (?, ?) 03:26:27,171 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: null 03:26:27,171 ERROR [JDBCExceptionReporter] Batch entry 0 insert into testfoo (test_foo, id) values (Diego, 2) was aborted. Call getNextException to see the cause. 03:26:27,171 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: 23505 03:26:27,171 ERROR [JDBCExceptionReporter] ERROR: duplicate key violates unique constraint "test_foo_dup_test" If you provide a failing test, we can take another look at this. Closing as "Cannot reproduce". > ConstraintViolationException returns null with PostgresDialect (Solution included) > ---------------------------------------------------------------------------------- > > Key: HHH-1599 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1599 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.1.3 > Environment: Hibernate 3.1.3 , Postgres 8.1.2 (i686), postgresql-8.2dev-501.jdbc.jar > Reporter: Niclas Lindberg > Assignee: Diego Pires Plentz > Priority: Minor > Attachments: HHH-1599-postgres-only.patch, HHH-1599.patch > > Original Estimate: 3 minutes > Remaining Estimate: 3 minutes > > ConstraintViolationException.getConstraintName() returns null. The problem is that the message being parsed comes from the SqlException that is the inputparameter to extractConstraintName(SqlException) in ViolatedConstraintNameExtracter. > Solution. The message provided by sqlException.getMessage() is "batch bla bla something" but the correct Exception message to parse is sqlException.getNextException().getMessage() -- 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

16 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2359) CallableStatement support for PostgreSQLDialect

by Jeroen van Vianen (JIRA)

CallableStatement support for PostgreSQLDialect ----------------------------------------------- Key: HHH-2359 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2359 Project: Hibernate3 Type: New Feature Components: core Versions: 3.2.1 Environment: Java JDK 1.5, Windows XP SP2, Hibernate 3.2.1, PostgreSQL 8.2.x, JDBC Driver 504 Reporter: Jeroen van Vianen Priority: Minor Attachments: postgresql-patch.txt This patch adds support for CallableStatements returning ResultSet in the PostgreSQLDialect by providing an implementation for: public int registerResultSetOutParameter(CallableStatement statement, int col) throws SQLException and public ResultSet getResultSet(CallableStatement ps) throws SQLException It follows the coding outlined in the PostgreSQL documentation at http://jdbc.postgresql.org/documentation/82/callproc.html#get-refcursor-f... -- 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

16 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Commented: (HBX-376) Support the ability to enable h3 filters and set parameters while doing hql queries

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-376?page=co... ] Max Rydahl Andersen commented on HBX-376: ----------------------------------------- Then maybe it is because I don't understand your initial report: "It would be helpful to support the ability to enable h3 filters and set parameters while doing hql queries" - I thought that meant you wanted to be able to set these parameters when you execute hql queries with the query editor. I did not understood that as somethign to be about codegeneration. > Support the ability to enable h3 filters and set parameters while doing hql queries > ----------------------------------------------------------------------------------- > > Key: HBX-376 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-376 > Project: Hibernate Tools > Issue Type: New Feature > Components: consoleconfiguration > Affects Versions: 3.1alpha5 > Reporter: Keith Garry Boyce > Fix For: 3.2LATER > > > It would be helpful to support the ability to enable h3 filters and set parameters while doing hql queries -- 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

16 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-376) Support the ability to enable h3 filters and set parameters while doing hql queries

by Keith Garry Boyce (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-376?page=co... ] Keith Garry Boyce commented on HBX-376: --------------------------------------- I don't understand your question really? The filters get put in hbm.xml files. > Support the ability to enable h3 filters and set parameters while doing hql queries > ----------------------------------------------------------------------------------- > > Key: HBX-376 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-376 > Project: Hibernate Tools > Issue Type: New Feature > Components: consoleconfiguration > Affects Versions: 3.1alpha5 > Reporter: Keith Garry Boyce > Fix For: 3.2LATER > > > It would be helpful to support the ability to enable h3 filters and set parameters while doing hql queries -- 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

16 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-680) oneToMany relationship, in which the source table column does NOT contain a unique constraint

by Sabina Schneider (JIRA)

oneToMany relationship, in which the source table column does NOT contain a unique constraint --------------------------------------------------------------------------------------------- Key: ANN-680 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-680 Project: Hibernate Annotations Issue Type: New Feature Affects Versions: 3.2.1 Environment: annotations version 3.2.1.ga, java 1.5 Reporter: Sabina Schneider I am particulary interested in generating a oneToMany relationship, in which the source table column does NOT contain a unique constraint. Nevertheless, specifying the referencedColumnName creates a unique constraint. How can I avoid this? This is the code: @OneToMany(targetEntity = AppleGenre.class, fetch=FetchType.LAZY) @LazyCollection(LazyCollectionOption.EXTRA) @JoinTable(name = "APPLE_FEATURE", joinColumns = { @JoinColumn(name = "APPLEID", referencedColumnName="APPLE_ID", unique=false, nullable=false, insertable=false, updatable=false ) }, inverseJoinColumns = { @JoinColumn(name = "WORD", referencedColumnName="APPLEGENREID ", unique=false, nullable=false, insertable=false, updatable=false) } ) public List<SoftGenre> getSoftGenres(){ return softGenres; } APPLE_ID is NOT unique and APPLEGENREID is PK of AppleGenre -- 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

16 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Commented: (HBX-376) Support the ability to enable h3 filters and set parameters while doing hql queries

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-376?page=co... ] Max Rydahl Andersen commented on HBX-376: ----------------------------------------- how does code generation settings help when doing hql queries ? > Support the ability to enable h3 filters and set parameters while doing hql queries > ----------------------------------------------------------------------------------- > > Key: HBX-376 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-376 > Project: Hibernate Tools > Issue Type: New Feature > Components: consoleconfiguration > Affects Versions: 3.1alpha5 > Reporter: Keith Garry Boyce > Fix For: 3.2LATER > > > It would be helpful to support the ability to enable h3 filters and set parameters while doing hql queries -- 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

16 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-376) Support the ability to enable h3 filters and set parameters while doing hql queries

by Keith Garry Boyce (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-376?page=co... ] Keith Garry Boyce commented on HBX-376: --------------------------------------- This can be done with simple meta tag.. No real need to wait till 3.2 or later... Currently I have created custom templates and what I'm doing is as follows: <meta attribute="hbm-code"> <![CDATA[ <filter name="invoiceVendorFilter" condition="BILL_DATE < :months"/> <filter name="vendorFilter" condition="VENDOR_CODE = :vendorCode"/> ]]> </meta> Just should be supported with out of the box with existing templates > Support the ability to enable h3 filters and set parameters while doing hql queries > ----------------------------------------------------------------------------------- > > Key: HBX-376 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-376 > Project: Hibernate Tools > Issue Type: New Feature > Components: consoleconfiguration > Affects Versions: 3.1alpha5 > Reporter: Keith Garry Boyce > Fix For: 3.2LATER > > > It would be helpful to support the ability to enable h3 filters and set parameters while doing hql queries -- 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

16 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2950) Add the ability for filters to cause columns to be retrieved or set in sql only when enabled through mappings

by Keith Garry Boyce (JIRA)

Add the ability for filters to cause columns to be retrieved or set in sql only when enabled through mappings ------------------------------------------------------------------------------------------------------------- Key: HHH-2950 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2950 Project: Hibernate3 Issue Type: Improvement Affects Versions: 3.2.2 Reporter: Keith Garry Boyce I need the abiltity to be able to protect certain columns from view or update unless a H3 filter is enabled. This is for security reasons. I propose a tag like include-unless shown below that can be applied to column. On retrieval if that filter is not enabled then the value of that column will not be retreived and on attempt to persist that data then that column will not be saved if it was not included on the db retrieve or if the filter is enabled. Here is an example <hibernate-mapping> <class name="com.xxx.Status" table="STATUS"> <id name="statusId" type="big_decimal"> <column name="STATUS_ID" precision="38" scale="0" /> <generator class="assigned" /> </id> <property name="lastName" type="string"> <column name="LAST_NAME" length="20" not-null="true" include-unless="myRestrictedFilter"> </column> </property> This mapping would result in the following if myRestrictedFilter was enabled: select from db would not include column LAST_NAME and update would not include column LAST_NAME -- 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

16 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-678) NPE when using JBoss 4.2 and @OneToOne annotation

by Yuval (JIRA)

NPE when using JBoss 4.2 and @OneToOne annotation ------------------------------------------------- Key: ANN-678 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-678 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.2.1 Environment: Annotations 3.2.1.ga , Hibernate 3.2.3.ga, entity-manager 3.2.1.ga. JDK 1.5, JBoss 4.2.0, Ubuntu, MySQL 5, SVN, Maven 2 Reporter: Yuval As former posts of this same problem, when we use bidirectional OneToOne relations We get NullPointerException. It is quite an odd problem since this problem is not consistent. I built my sources and had this problem consistently, then when I changed the name of the folder I checked out the code to, built again and then deployed on JBoss, it worked OK. Meaning the mappedBy text and the rest of the annotation setup is ok. I saw this issue is supposed to be resolved in 3.3.1 BUT Jboss 4.2 does not work with 3.3.1 due to backward incompatibility issues. So a fix for 3.2.1 is necessary. I can past the stack trace but it is exactly the same to former posts on this same issue. -- 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

16 years, 6 months

3
4
0 / 0

[Hibernate-JIRA] Commented: (HHH-759) problem for mixxing setmaxresults and setlockmode

by Frederic Leitenberger (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-759?page=co... ] Frederic Leitenberger commented on HHH-759: ------------------------------------------- Hello again, i have serous trouble with this. I need to use ORDER BY, MAXROWS and FOR UPDATE in one query. e.g.: Criteria criteria = getSession().createCriteria(MyClass.class) .add(Restrictions.eq("myField", false)) .add(Order.desc("oderField")) .setLockMode(LockMode.UPGRADE) .setMaxResults(1); What i want form this query is: - select the rows for my restricitions - order the result - limit the result - lock the result What it currently get (simplified) is: select * from ( select * from myClass where myField = 0 order by usage desc ) where rownum <= ? for update of this_.id As we already know this doesn't work: org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:2223) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104) at org.hibernate.loader.Loader.list(Loader.java:2099) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:94) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1569) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:283) at de.iccs.api.facades.ResellerBlockFacade.listResellerFreeBlocksForAssignment(ResellerBlockFacade.java:245) at de.iccs.api.facades.ResellerBlockFacade.allocateNumbersInternal(ResellerBlockFacade.java:1095) at de.iccs.api.facades.GeoNumberFacade.allocateGeoNumbersInternal(GeoNumberFacade.java:979) at de.iccs.api.facades.GeoNumberFacade.reserveGeoNumbersInternal(GeoNumberFacade.java:938) at de.iccs.api.facades.GeoNumberFacade.allocateGeoNumbersForAllocateEleven(GeoNumberFacade.java:798) at de.iccs.api.facades.GeoNumberFacade$$EnhancerByCGLIB$$cf19ce9a.CGLIB$allocateGeoNumbersForAllocateEleven$2(<generated>) at de.iccs.api.facades.GeoNumberFacade$$EnhancerByCGLIB$$cf19ce9a$$FastClassByCGLIB$$2ccb1367.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:167) at de.iccs.api.facades.interceptors.FacadeInterceptor.intercept(FacadeInterceptor.java:17) at de.iccs.api.facades.interceptors.HibernateFacadeInterceptor.intercept(HibernateFacadeInterceptor.java:82) at de.iccs.api.facades.GeoNumberFacade$$EnhancerByCGLIB$$cf19ce9a.allocateGeoNumbersForAllocateEleven(<generated>) at de.iccs.api.facades.GeoNumberFacadeTest.testAllocateGeoNumbersForAllocateEleven(GeoNumberFacadeTest.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.sql.SQLException: ORA-00904: "THIS_"."ID": invalid identifier at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:305) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:272) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:623) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:181) at oracle.jdbc.driver.T4CPreparedStatement.execute_for_describe(T4CPreparedStatement.java:420) at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:896) at oracle.jdbc.driver.T4CPreparedStatement.execute_maybe_describe(T4CPreparedStatement.java:452) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:986) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2888) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:2929) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186) at org.hibernate.loader.Loader.getResultSet(Loader.java:1787) at org.hibernate.loader.Loader.doQuery(Loader.java:674) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.doList(Loader.java:2220) ... 33 more When i change the setMaxRows-call to: if (maxResults > 0) criteria.add(sqlRestriction("rownum <= ?", maxResults, new IntegerType())); ... or simply ... criteria.add(Restrictions.sqlRestriction("rownum <= 1")); ... the following is generated: select * from myClass where myField = 0 and rownum <= ? order by usage desc for update of this_.id The statement can be executed, but does the following (in exaclty this order): - select the rows for my restricitions - limit the result (unordered) - order the result (the one selected row) - lock the result For comparison again what i wanted form this query: - select the rows for my restricitions - order the result - limit the result - lock the result Any idea how to solve this? I had an idea of selecting and locking only an id, but i am still not sure if that solves the problem in any way. Another idea was to drop the setMaxRows part and user iterate to get as many rows as needed an then close the iterator and cursor with Hibernate.closeIterator(iter). But HB-308 and HHH-249 indicate that this will not be available very soon considering the comments and the last-modified timestamps. And since it would we somewhat difficult and stupid to bypass the critera-functionality i am stuck here. Any help would be great ! > problem for mixxing setmaxresults and setlockmode > ------------------------------------------------- > > Key: HHH-759 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-759 > Project: Hibernate3 > Issue Type: Bug > Affects Versions: 3.0.2 > Environment: Client:windows2000 professional,jre1.4.2, oracle8client,eclipse3.1-RC3,hibernate-tools 3.0 alpha4a,JBossIDE1.5M1 > Server:Solaris 2.8, oracle 8.1.7 > Reporter: johnhua > Priority: Minor > > there is a problem for mixxing setmaxresults and setlockmode. > the problem is that "ORA-00904: invalid column name". > The error info is as the below: > Hibernate: select * from ( select idmapp0_.RI as col_0_0_ from PCTMNGT.IDMAP_P idmapp0_ where idmapp0_.STATUS=? ) where rownum <= ? for update of idmapp0_.RI > 14:21:54,076 DEBUG AbstractBatcher:AbstractBatcher.java:365 - preparing statement > 14:21:54,082 DEBUG AbstractBatcher:AbstractBatcher.java:285 - about to close PreparedStatement (open PreparedStatements: 1, globally: 1) > 14:21:54,083 DEBUG AbstractBatcher:AbstractBatcher.java:403 - closing statement > 14:21:54,090 WARN JDBCExceptionReporter:JDBCExceptionReporter.java:71 - SQL Error: 904, SQLState: 42000 > 14:21:54,091 ERROR JDBCExceptionReporter:JDBCExceptionReporter.java:72 - ORA-00904: invalid column name > The source code is as the below: > //query an unused emid for new tone > query = av_session.createQuery("select v_idmap from IdmapP as v_idmap where v_idmap.status=:v_status"); > query.setCharacter("v_status",EMID_STATUS.UNUSED.charValue()); > query.setMaxResults(1); > query.setLockMode("v_idmap",LockMode.UPGRADE); > it = query.iterate(); > if( !it.hasNext() ) > { > tx.rollback(); > lv_err = "addRing::doAddRingFile: no unused EMID for new tone in idmap. toneid="+av_tone; > throw new InterfaceErrException(lv_err,INTERFACE_RETCODE.SYSTEM_ERR); > } -- 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

16 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2007