August 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Updated: (HHH-1083) Customization of CREATE TABLE with storage clause etc.

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1083?page=c... ] Steve Ebersole updated HHH-1083: -------------------------------- Fix Version/s: (was: 4.0.0.CR1) metamodel > Customization of CREATE TABLE with storage clause etc. > ------------------------------------------------------ > > Key: HHH-1083 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1083 > Project: Hibernate Core > Issue Type: New Feature > Components: core > Reporter: Christian Bauer > Assignee: Steve Ebersole > Priority: Minor > Fix For: metamodel > > > Currently Hibernate features a hotfix for the MySQLInnoDBDialect: > public String getTableTypeString() { > return " type=InnoDB"; > } > However, this is not the only appendix that is useful for CREATE TABLE. We should do several things: > - allow appendix for CREATE INDEX, for example, to define the tablespace > - pass in additional arguments to getTableTypeString(), such as tableName, schemaName, catalogName - for example, to allow custom Dialects to return different tablespaces for particular tables > - probably rename the getTableTypeString() method to getTableAppendixString() and getIndexAppendixString() -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-6584) HSQLDB dialect : wrong type in generated DDL for BigDecimal

by Vianney Carel (JIRA)

HSQLDB dialect : wrong type in generated DDL for BigDecimal ----------------------------------------------------------- Key: HHH-6584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6584 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.3.1 Reporter: Vianney Carel Attachments: Invoice.zip Hi, I get a wrong column type in the generated DDL when using the @Column annotation for a BigDecimal property. My Java code: @Column public BigDecimal getAmount() { return amount; } The generated table creation instruction : create table inv_invoice (id bigint not null, amount numeric, primary key (id)) The generated type should be "decimal" (with optionaly precision and scale) and not "numeric". Thanks, -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-848) Isolated failures in backend work operations don't affect subsequent operations in same workQueue

by Sanne Grinovero (JIRA)

Isolated failures in backend work operations don't affect subsequent operations in same workQueue ------------------------------------------------------------------------------------------------- Key: HSEARCH-848 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-848 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.0.0.Alpha1 With the new Hibernate Search backend, since we don't need to mandate order of LuceneWork operations, it's not needed to abort the full queue when a single operation fails. In practice since they are now applied in parallel, it's more effective and simpler to leave out this logic which was previously a requirement. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-850) Some InterruptedExceptions don't restore the interrupted thread state

by Sanne Grinovero (JIRA)

Some InterruptedExceptions don't restore the interrupted thread state --------------------------------------------------------------------- Key: HSEARCH-850 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-850 Project: Hibernate Search Issue Type: Bug Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.0.0.Alpha1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-845) Update JBoss Logger to 3.0.0.GA

by Sanne Grinovero (JIRA)

Update JBoss Logger to 3.0.0.GA ------------------------------- Key: HSEARCH-845 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-845 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-844) Update Byteman to version 1.5.2

by Sanne Grinovero (JIRA)

Update Byteman to version 1.5.2 ------------------------------- Key: HSEARCH-844 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-844 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial Fix For: 4.0.0.Alpha1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-626) Allow MassIndexer to work in parallel of regular indexing / querying

by Emmanuel Bernard (JIRA)

Allow MassIndexer to work in parallel of regular indexing / querying -------------------------------------------------------------------- Key: HSEARCH-626 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-626 Project: Hibernate Search Issue Type: New Feature Components: massindexer Reporter: Emmanuel Bernard Some people want to use mass indexer to reindex live some data. This is problematic today as MassIndexer expects to work alone / offline. I can see at least one approach: - copy the index to a new Directory before mass indexing (or if exclusive, start with a new Directory while keeping the old Directory in place - the current directory needs to become read-only - all index update (on the entity) requests should be queued up for after massIndexer is done - MassIndexer swaps the current and the new directory - indexing and querying resume as normal Note that we need to work on a different directory because mass indexer does delete all entries of an entity before starting the reindexing process. -- 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

14 years, 1 month

2
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-762) enabled exclusive_index_use=true by default

by Sanne Grinovero (JIRA)

enabled exclusive_index_use=true by default ------------------------------------------- Key: HSEARCH-762 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-762 Project: Hibernate Search Issue Type: Improvement Components: documentation, engine Reporter: Sanne Grinovero Fix For: 4.0.0.Alpha1 great performance improvement, while this was the recommended configuration it wasn't enabled by default for backwards compatibility. -- 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

14 years, 1 month

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-6582) Schema validation fails on HSQLDB for @Type(type="text") fields

by Thilo-Alexander Ginkel (JIRA)

Schema validation fails on HSQLDB for @Type(type="text") fields --------------------------------------------------------------- Key: HHH-6582 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6582 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.6 Environment: Hibernate 3.6.6, HSQLDB 2.2.4 Reporter: Thilo-Alexander Ginkel When declaring an entity's field as @Column(name = "description", nullable = true) @Type(type="text") the schema validation fails with the following error message on HSQLDB: org.hibernate.HibernateException: Wrong column type in <table> for column description. Found: varchar, expected: longvarchar at org.hibernate.mapping.Table.validateColumns(Table.java:283) at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:1343) at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:139) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:378) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1872) at org.springframework.orm.hibernate3.LocalSessionFactoryBean.newSessionFactory(LocalSessionFactoryBean.java:855) at org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:774) [...] Apparently, HSQLDB maps the longvarchar column generated by Hibernate into a varchar(16M), which confuses the validator. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-6579) Failure to determine data type in field access mode

by Markus Mårtensson (JIRA)

Failure to determine data type in field access mode --------------------------------------------------- Key: HHH-6579 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6579 Project: Hibernate Core Issue Type: Bug Components: annotations, metamodel Affects Versions: 4.0.0.Beta5 Environment: Hibernate 4.0.0-Beta5 (org.hibernate.dialect.MySQLDialect) Reporter: Markus Mårtensson The below class, when passed through buildServiceRegistry() and buildMetadata() will determine data type for "withGetter", but not for "withoutGetter". The placement of @Id sets the class into field access mode and correctly picks up both fields, but fields without a getter needs an explicit @Type annotation. The expected behavior is for both fields to have their types determined. @Entity public class Bugged { @Id Long withoutGetter; Long withGetter; public Long getWithGetter() { return withGetter; } } Datatype detection log excerpt follows: 11:20:14.423 [main] DEBUG o.h.m.relational.AbstractSimpleValue - setting datatype for column `Bugged`.`withoutGetter` : null 11:20:14.427 [main] DEBUG o.h.m.relational.AbstractSimpleValue - setting datatype for column `Bugged`.`withGetter` : null 11:20:14.433 [main] DEBUG o.h.m.relational.AbstractSimpleValue - setting datatype for column `Bugged`.`withGetter` : org.hibernate.metamodel.relational.Datatype@76303ac7[code=-5, name=long, javaClass=java.lang.Long] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2011