July 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] (HHH-7404) [JPA] Double insert with @OneToMany and CASCADE.ALL

by mcbain4711 (JIRA)

13 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-269) Spell check functionality needed

by John Griffin (JIRA)

Spell check functionality needed -------------------------------- Key: HSEARCH-269 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-269 Project: Hibernate Search Issue Type: New Feature Components: engine, mapping Affects Versions: 3.2.0 Reporter: John Griffin Assignee: John Griffin >From Emmanuel: - more than one field and even more than one index should be the source of the dictionary - declaring which field is part of a dictionary should be declarative @AddToDictionary(name="main-dictionary") (with probably an optional field name(s)) - for a given dictionary name, we need to associate an index and probably a field prefix (to share the same index for all dictionaries). This couold be by annotations or in the configuration (not sure) - this index should be kept like any other DirectoryProvider in the HSearch intrastructure (we could then reuse ReaderProvider internally and don't have leaks). - we will probably add a manual dictionary reindex method and the SpellChecker API should be in the SearchFactory. sf.getDictionary("main-dictionary").spellcheck(word, suggestion); sf.getDictionary("main-dictionary").spellcheck(word, suggestion, entity, properties...); //not sure how useful is this one really sf.getDictionary("main-dictionary").reindex(); this needs to be refined. -- 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, 6 months

5
13
0 / 0

[Hibernate-JIRA] Created: (OGM-70) Describe how to run a cluster of Infinispan nodes with Hibernate OGM (both tutorial and main reference articles)

by Emmanuel Bernard (JIRA)

Describe how to run a cluster of Infinispan nodes with Hibernate OGM (both tutorial and main reference articles) ---------------------------------------------------------------------------------------------------------------- Key: OGM-70 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-70 Project: Hibernate OGM Issue Type: Task Components: documentation Reporter: Emmanuel Bernard Assignee: Sanne Grinovero There is a todo in the tutorial to let people start a second node in the grid. The idea is to tell people to use the same configuration file. We could possibly give in the distribution a helper class or helper main that start Infinispan and start the various necessary caches. (that could be a different JIRA). -- 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, 6 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4098) VARBINARY should be BLOB in DB2400Dialect

by Christian Luebke (JIRA)

VARBINARY should be BLOB in DB2400Dialect ----------------------------------------- Key: HHH-4098 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4098 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.0.Beta-1 Environment: tested with hibernate 3.2.6ga, IBM DB2/400 on i5/os V5R4 Reporter: Christian Luebke Priority: Minor VARBINARY is registered in DB2Dialect (superclass of DB2400Dialect) as "varchar($l) for bit data". As DB2/400 (aka IBM DB2 for i) has a record length limitation of 32766 bytes, VARBINARY should be implemented as BLOB. Blobs are being stored outside the db record. I successfully tried adding the following constructor in DB2400Dialect.java: public DB2400Dialect() { super(); registerColumnType( Types.VARBINARY, "blob($l)" ); } As I'm not a hibernate user by myself, I can't provide a test case. I tried to get Bonita Workflow (http://www.bonitasoft.com/) to run with my DB2/400. It failed initially because of the usage of a 64 K varbinary. After patching DB2400Dialect to use a blob, everything worked fine. -- 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, 6 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2651) Map binary types for sizes > 32K to BLOB for Derby

by Vincent Massol (JIRA)

Map binary types for sizes > 32K to BLOB for Derby -------------------------------------------------- Key: HHH-2651 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2651 Project: Hibernate3 Issue Type: Improvement Components: metamodel Affects Versions: 3.1.2 Reporter: Vincent Massol Right now (at least with 3.1.2, haven't tried with more recent versions) the binary type is mapped to a VARCHAR. However VARCHARs in Derby have a max size of 32K. So for sized larger than 32K a BLOB should be used instead. -- 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, 6 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2697) Can't use := for variable assignment within a SQL-Statement

by Benjamin Gniza (JIRA)

Can't use := for variable assignment within a SQL-Statement ----------------------------------------------------------- Key: HHH-2697 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2697 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4.sp1 Environment: MySQL Datasource, Hibernate 3.2.4.sp1 Reporter: Benjamin Gniza Priority: Minor i found a kind of bug in org.hibernate.engine.query.ParameterParser.java: I have an exotic mysql-statement where I want to use mysql variables. VERY SIMPLE example: SET @pos=0; SELECT @pos:=@pos+1 FROM TABLE; Steps to reproduce: Session s = sessionFactory.openSession(); s.createSQLQuery("SET @pos=0").executeUpdate(); SQLQuery qry = s.createSQLQuery("select @pos:=@pos from SomeTable"); List lst = qry.list(); Exception: org.hibernate.QueryException: Space is not allowed after parameter prefix ':' 'SELECT @pos:=@pos+1 FROM TABLE' at org.hibernate.engine.query.ParameterParser.parse(ParameterParser.java:68) ... ... Suggested fix: ParameterParser Lines 62 to 73: if (c == ':' && (indx + 1 >= stringLength || sqlString.charAt(indx + 1) != '=')) { // named parameter int right = StringHelper.firstIndexOfChar( sqlString, ParserHelper.HQL_SEPARATORS, indx + 1 ); int chopLocation = right < 0 ? sqlString.length() : right; String param = sqlString.substring( indx + 1, chopLocation ); if ( StringHelper.isEmpty( param ) ) { throw new QueryException("Space is not allowed after parameter prefix ':' '" + sqlString + "'"); } recognizer.namedParameter( param, indx ); indx = chopLocation - 1; } -- 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, 6 months

15
22
0 / 0

[Hibernate-JIRA] Created: (OGM-164) When persistence provider is not specified the EMF creation taking a PersistenceUnitInfo defaults to OGM instead of plain ORM

by Sanne Grinovero (JIRA)

When persistence provider is not specified the EMF creation taking a PersistenceUnitInfo defaults to OGM instead of plain ORM ----------------------------------------------------------------------------------------------------------------------------- Key: OGM-164 URL: https://hibernate.onjira.com/browse/OGM-164 Project: Hibernate OGM Issue Type: Bug Components: core Reporter: Sanne Grinovero Fix For: 4.0-next Basically the method org.hibernate.ogm.jpa.HibernateOgmPersistence.createContainerEntityManagerFactory(PersistenceUnitInfo, Map) should not have the check on {code}persistenceProviderClassName == null{code} but return null. trivial fix but requires a test as this wasn't covered. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (OGM-138) Some tests don't cleanup after failure

by Sanne Grinovero (JIRA)

Some tests don't cleanup after failure -------------------------------------- Key: OGM-138 URL: https://hibernate.onjira.com/browse/OGM-138 Project: Hibernate OGM Issue Type: Bug Reporter: Sanne Grinovero Fix For: 4.0-next Some tests are not cleaning up. When running the testsuite and having many failures (because of implementation problems) some errors show {quote} ARJUNA016051: thread is already associated with a transaction! {quote} While the test is opening it's first transaction. I guess some other test didn't close it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
3
0 / 0

[Hibernate-JIRA] Created: (OGM-136) Update architecture schema to reflect DatastoreProvider and GridDialect

by Emmanuel Bernard (JIRA)

Update architecture schema to reflect DatastoreProvider and GridDialect ----------------------------------------------------------------------- Key: OGM-136 URL: https://hibernate.onjira.com/browse/OGM-136 Project: Hibernate OGM Issue Type: Task Components: documentation Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (OGM-159) Provide the list of column names to the Dialect for an entity and association operation

by Emmanuel Bernard (JIRA)

Provide the list of column names to the Dialect for an entity and association operation --------------------------------------------------------------------------------------- Key: OGM-159 URL: https://hibernate.onjira.com/browse/OGM-159 Project: Hibernate OGM Issue Type: Improvement Components: datastore Environment: That can help some nosql to reduce network traffic and workload Reporter: Emmanuel Bernard -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2012