January 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-382) Indexing fails silently in case the file based index is mounted read only

by Hardy Ferentschik (JIRA)

Indexing fails silently in case the file based index is mounted read only ------------------------------------------------------------------------- Key: HSEARCH-382 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-382 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.1.GA Reporter: Hardy Ferentschik Fix For: 3.2.0 I haven't confirmed this yet, but we should investigate this - https://forum.hibernate.org/viewtopic.php?f=9&t=997789 -- 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, 2 months

3
7
0 / 0

[Hibernate-JIRA] Created: (METAGEN-13) Only re-process xml files if thay have changed

by Hardy Ferentschik (JIRA)

Only re-process xml files if thay have changed ---------------------------------------------- Key: METAGEN-13 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-13 Project: Hibernate StaticMetamodel Generator Issue Type: Improvement Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Optimize XML parsing by only processing XML files if they have changed since last run. There are no API hooks to do this. Maybe write a tmp file against which to compare the last modified time stamp. Maybe this is a task for IDE integration!? -- 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, 2 months

1
4
0 / 0

[Hibernate-JIRA] Created: (METAGEN-4) Document how to use the processor in different environments

by Hardy Ferentschik (JIRA)

Document how to use the processor in different environments ----------------------------------------------------------- Key: METAGEN-4 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-4 Project: Hibernate StaticMetamodel Generator Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Include the documentation into the project (docbook?!) and blog about it. -- 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, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3841) Add support for lock timeouts

by Christian Daszenies (JIRA)

Add support for lock timeouts ------------------------------ Key: HHH-3841 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3841 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Christian Daszenies It would be nice to support (pessimistic) lock timeouts, as with Oracle's SELECT ... FOR UPDATE WAIT [seconds] syntax. There has been an issue in Project hibernate2 (HB-950) with the same request. -- 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, 2 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4765) Enhance Dialect support for JPA-2 locking

by Scott Marlow (JIRA)

Enhance Dialect support for JPA-2 locking ----------------------------------------- Key: HHH-4765 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4765 Project: Hibernate Core Issue Type: Sub-task Components: core Affects Versions: 3.5.0-Beta-2 Reporter: Scott Marlow Fix For: 3.5 Follow up issue for JPA-2 locking support. HHH-4546 added JPA-2 locking support in Hibernate core and the Derby dialect. This jira is about completing that work by enhancing dialects to fully support JPA-2 locking (pessistic read/write lock with timeout). As part of the HHH-4546 effort, all dialects currently have support for JPA-2 optimistic locking. All dialects also currently fullfil the JPA-2 specification requirements for pessimistic locking (e.g. write locks can be used in place of read locks). -- 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, 2 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-87) Avoid to trigger optimization during intermediate batches

by Emmanuel Bernard (JIRA)

Avoid to trigger optimization during intermediate batches --------------------------------------------------------- Key: HSEARCH-87 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-87 Project: Hibernate Search Issue Type: New Feature Reporter: Emmanuel Bernard A queue can be batched (esp session.index()) optimization should be delayed for the end of the transaction -- 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, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4836) Infinispan: 2L QueryCache don't considers cached queries which belong to current transaction

by Guenther Demetz (JIRA)

Infinispan: 2L QueryCache don't considers cached queries which belong to current transaction -------------------------------------------------------------------------------------------- Key: HHH-4836 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4836 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1 Environment: 3.5.0.Beta3, SQLServerr2008, integration with JTA Reporter: Guenther Demetz When looking for a cached Query in 2L-cache, QueryResultsRegionImpl(BaseRegion) does temporary suspend the current transaction. QueryResultsRegionImpl(BaseRegion).suspendAndGet(Object, FlagAdapter, boolean) line: 205 In this way only committed queries from already closed transactions are considered to be hit. Cached queries put by the current transaction are totally ignored! This is in my opinion a bug, because it changes behavior and degrades the efficiency of the 2L QueryCache in respect to other 2L-implementations (for example EHCache). Furthermore there is no reason to ignore cached queries deriving from current transaction: the up-to-date-ness is checked anyway by the StandardQueryCache.isUpToDate() call. Proposed solution: simply not suspend current transaction when looking for cached querys, then queries put by the current transaction are automatically considered as candidates for a hit. -- 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, 2 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3125) BigDecimal support for id generator from DB sequence

by Tomas Rada (JIRA)

BigDecimal support for id generator from DB sequence ---------------------------------------------------- Key: HHH-3125 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3125 Project: Hibernate3 Issue Type: New Feature Environment: Hibernate 3.2, Oracle 10 Reporter: Tomas Rada Currently with using BigDecimal as entity id is thrown exception " this id generator generates long, integer, short or string" - class "IdentifierGeneratorFactory". Is there possibility to add BigDecimal support for id generator? -- 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, 2 months

6
9
0 / 0

[Hibernate-JIRA] Created: (HHH-4639) Allow JPA SequenceGenerator (SequenceHiLoGenerator) generate BigInteger value

by Alexey Tomin (JIRA)

Allow JPA SequenceGenerator (SequenceHiLoGenerator) generate BigInteger value ----------------------------------------------------------------------------- Key: HHH-4639 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4639 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.5.0-Beta-2 Environment: 3.5.0-Beta-2 from jboss-6.0.0.M1 Oracle 10g Reporter: Alexey Tomin Attachments: BigInteger.patch In database (oracle) we used number(38) identifiers create sequence T_SEQ minvalue 1 maxvalue 999999999999999999999999999 start with 10000000000000044968 increment by 1; Version 3.5.0-beta-2 can not generate identifiers more, then long (number(19)). I create minimal (no optimal) patch -- 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, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3968) Error in SchemaUpdate using HSQLDialect with BigInteger or BigDecimal primary keys [similar to HHH.3323]

by Jonathan Mastin (JIRA)

Error in SchemaUpdate using HSQLDialect with BigInteger or BigDecimal primary keys [similar to HHH.3323] -------------------------------------------------------------------------------------------------------- Key: HHH-3968 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3968 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.0.SP1 Environment: HSQLDB: 1.8.0.9 Reporter: Jonathan Mastin Problem --------------- When using HSQLDialect, the following code fails during schema creation: @Entity public class Test { @Id @GeneratedValue(strategy = GenerationType.AUTO) private BigInteger id; } Log output: ---------------- ERROR org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: create table Test (id numeric generated by default as identity (start with 1), primary key (id)) ERROR org.hibernate.tool.hbm2ddl.SchemaUpdate - Wrong data type: id in statement [create table Test (id numeric generated by default as identity (start with 1)] Expected --------------------------------- The column type is being set as "numeric", but it needs to be set as "integer" or "bigint" for HSQL to be able to parse. >From the HSQL manual: "The supported form is(<colname> INTEGER GENERATED BY DEFAULT AS IDENTITY(START WITH n, [INCREMENT BY m])PRIMARY KEY, ...). Support has also been added for BIGINT identity columns. As a result, an IDENTITY column is simply an INTEGER or BIGINT column ..." -- 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, 2 months

2
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 January 2010