November 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4539) Make UPPER and LOWER work on MS SQL Server text and ntext columns

by Sergiu Dumitriu (JIRA)

Make UPPER and LOWER work on MS SQL Server text and ntext columns ----------------------------------------------------------------- Key: HHH-4539 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4539 Project: Hibernate Core Issue Type: Improvement Components: query-sql Affects Versions: 3.3.2 Environment: MS SQL Server Reporter: Sergiu Dumitriu Trying to use UPPER or LOWER on a text column results in: ERROR util.JDBCExceptionReporter - Argument data type text is invalid for argument 1 of upper function. http://databases.aspfaq.com/database/why-do-i-get-argument-data-type-text... suggests a workaround, which I think should be automatically used by Hibernate, so that the HQL query can work with other dialects. -- 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

13 years, 7 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5726) SqlServerDialect should support variable limit

by Yoryos Valotassios (JIRA)

SqlServerDialect should support variable limit ---------------------------------------------- Key: HHH-5726 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5726 Project: Hibernate Core Issue Type: Bug Reporter: Yoryos Valotassios The SqlServerDialect using the row_number function can support variable limit. At the end of the query, instead of binding the limit and offset to the between statement just use ? -- 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

13 years, 7 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5725) SqlServerDialect should support SQL 2000 which does not support the row_number function

by Yoryos Valotassios (JIRA)

SqlServerDialect should support SQL 2000 which does not support the row_number function --------------------------------------------------------------------------------------- Key: HHH-5725 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5725 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0 Reporter: Yoryos Valotassios As a fix to HHH-2655 a patch has been applied to SQLServerDialect that make use of the row_number function for paged results. As I can see from the comments of SQLServerDialect, this dialect should be fine for sql server 2000, but sql server 2000 does not support row_number function. There should be a new dialect that extends the SQLServerDialect one which will add support for paged results throw the row_number function. -- 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

13 years, 7 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3965) Expose the ability to use varchar(max) or nvarchar(max)

by Ido Ran (JIRA)

Expose the ability to use varchar(max) or nvarchar(max) ------------------------------------------------------- Key: HHH-3965 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3965 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.4.0GA as provider for JPA 1.0 - SQL Server 2005 Database Reporter: Ido Ran Priority: Blocker I have an entity which needs to store long text field (at least 30,000 characters). I use SQL Server 2005 as back-end database. SQL Server varchar support up-to 8,000 characters in length of a field, or the reserved word MAX which indicate that the field length will be 2^31-1. I think that the class SQLServerDialect should be changed to have the following line in it's ctor: registerColumnType( Types.VARCHAR, 8001, "varchar(MAX)" ); this way, all String fields with length above 8000 will have varchar(MAX) as column type. -- 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

13 years, 7 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-517) ThreadLocal in ContextHolder causes memory leak when deployed in a web container

by Vojtěch Krása (JIRA)

ThreadLocal in ContextHolder causes memory leak when deployed in a web container -------------------------------------------------------------------------------- Key: HSEARCH-517 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-517 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.2.0.CR1, 3.2.0.Beta1, 3.1.1.GA, 3.1.0.GA, 3.1.0.CR1, 3.1.0.Beta2, 3.1.0.Beta1, 3.0.1.GA, 3.0.0.GA Environment: Hibernate 3.4.0.GA/3.5.1-Final, Tomcat 6.0.26, Spring 2.5.6/3.0.1, Sun JDK 1.6; Hibernate 3.3.1.GA Tomcat 6.0.18 Spring 2.5.6 Java OpenJDK 1.6 Reporter: Vojtěch Krása Priority: Critical Attachments: dump.zip, testCase.zip The SearchFactory has a static ThreadLocal variables which holds a reference to the SearchFactoryImpl. The ThreadLocal is not cleared when the application is undeployed, causing a memory leak. http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-314 -- 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

13 years, 7 months

4
8
0 / 0

[Hibernate-JIRA] Created: (METAGEN-48) Distribution bundle does not contain jar artifact

by Hardy Ferentschik (JIRA)

Distribution bundle does not contain jar artifact ------------------------------------------------- Key: METAGEN-48 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-48 Project: Hibernate Metamodel Generator Issue Type: Bug Components: build Affects Versions: 1.1.0.Final Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 1.x Attachments: hibernate-jpamodelgen-1.1.0.Final-dist.tar.gz -- 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

13 years, 7 months

1
2
0 / 0

[Hibernate-JIRA] Created: (METAGEN-44) getting Runtime error message "o.h.e.m.MetadataContext - Unable to locate static metamodel field"

by Young Lee (JIRA)

getting Runtime error message "o.h.e.m.MetadataContext - Unable to locate static metamodel field" ------------------------------------------------------------------------------------------------- Key: METAGEN-44 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-44 Project: Hibernate Metamodel Generator Issue Type: Bug Affects Versions: 1.1.0.CR1 Reporter: Young Lee Assignee: Hardy Ferentschik Attachments: test.jar I have a @MappedSuperClass declared as @MappedSuperClass public abstract class IdentifiableComponent<T extends EmbeddableId> extends RecordTimestamp2 implements Serializable and my Entity class declared as @Entity public class AppRegistration extends IdentifiableComponent<AppRegistrationId> and the Composite Id class declared as @Embeddable public class AppRegistrationId implements EmbeddableId The metamodel is generated properly, but at runtime I get the following error message o.h.e.m.MetadataContext - Unable to locate static metamodel field : com.playspan.lookup.model.AppRegistration_#id I've tried adding @IdClass(AppRegistrationId) annotation to the AppRegistration Entity class, but still I get the same error message. Please tell me what I am doing wrong. Thanx in advance. Attached is a complete sample buildable maven project with the above classes -- 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

13 years, 7 months

2
4
0 / 0

[Hibernate-JIRA] Created: (METAGEN-49) JPAMetaModelEntityProcessor.createMetaModelClasses calls remove within foreach loop (causing a ConcurrentModificationException)

by Robin Sander (JIRA)

JPAMetaModelEntityProcessor.createMetaModelClasses calls remove within foreach loop (causing a ConcurrentModificationException) ------------------------------------------------------------------------------------------------------------------------------- Key: METAGEN-49 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-49 Project: Hibernate Metamodel Generator Issue Type: Bug Components: processor Affects Versions: 1.1.0.Final Environment: Hibernate 3.6.0, Java 6 (1.6.0_22), Mac OS X 10.6.5 Reporter: Robin Sander Assignee: Hardy Ferentschik Running the annotation processor causes a ConcurrentModificationException. I'm using Maven and the maven-processor-plugin 1.3.7 but from looking into the sources I guess this bug occurs in any environment. JPAMetaModelEntityProcessor.createMetaModelClasses iterates of a Collection<MetaEntity> using a foreach loop and calls remove on the same collection which causes a ConcurrentModificationException. Obviously an iterator should be used instead. Here are the lines concerned: {code:java} Collection<MetaEntity> toProcessEntities = context.getMetaEmbeddables(); while ( !toProcessEntities.isEmpty() ) { Set<MetaEntity> processedEntities = new HashSet<MetaEntity>(); int toProcessCountBeforeLoop = toProcessEntities.size(); for ( MetaEntity entity : toProcessEntities ) { // see METAGEN-36 if ( generatedModelClasses.contains( entity.getQualifiedName() ) ) { toProcessEntities.remove( entity ); // XXX this causes a ConcurrentModificationException continue; } ... {code} Here is the stacktrace: {code} ... [INFO] diagnostic Note: Hibernate JPA 2 Static-Metamodel Generator 1.1.0.Final An annotation processor threw an uncaught exception. Consult the following stack trace for details. java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) at java.util.HashMap$ValueIterator.next(HashMap.java:822) at org.hibernate.jpamodelgen.JPAMetaModelEntityProcessor.createMetaModelClasses(JPAMetaModelEntityProcessor.java:153) at org.hibernate.jpamodelgen.JPAMetaModelEntityProcessor.process(JPAMetaModelEntityProcessor.java:133) at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:625) at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:554) at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:699) at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:981) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:727) at com.sun.tools.javac.main.Main.compile(Main.java:353) at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:115) at org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.executeWithExceptionsHandled(AbstractAnnotationProcessorMojo.java:261) at org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.execute(AbstractAnnotationProcessorMojo.java:129) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) {code} -- 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

13 years, 7 months

2
8
0 / 0

[Hibernate-JIRA] Created: (METAGEN-47) Improve documentation on IntelliJ's configuration

by Emmanuel Bernard (JIRA)

Improve documentation on IntelliJ's configuration ------------------------------------------------- Key: METAGEN-47 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-47 Project: Hibernate Metamodel Generator Issue Type: Improvement Components: documentation Affects Versions: 1.1.0.Final Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 1.x -- 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

13 years, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5761) Update source repository links in Envers documentation

by Erik-Berndt Scheper (JIRA)

Update source repository links in Envers documentation ------------------------------------------------------- Key: HHH-5761 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5761 Project: Hibernate Core Issue Type: Improvement Components: envers Affects Versions: 3.6.0 Reporter: Erik-Berndt Scheper Assignee: Erik-Berndt Scheper Priority: Trivial Fix For: 3.6.1, 4.0.0.Alpha1 The Envers documentation still has a link to the old SVN repository. This should be updated to the new Git location. -- 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

13 years, 7 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2010