November 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-636) Add the annotations to map the User Collection Type

by jason (JIRA)

Add the annotations to map the User Collection Type --------------------------------------------------- Key: ANN-636 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-636 Project: Hibernate Annotations Issue Type: New Feature Components: binder Environment: n/a Reporter: jason I am searching a way from the Hibernate Annotation to map the user defined collection, and find out the following : Can anybody let me know what the status for this? or how i can map the user collection type by hibernate annotation, thanks Add an annotation to specify the UserCollectionType for a OneToMany or ManyToMany. The annotation is named CollectionTypeInfo, perhaps better named UserCollectionType, but I didn't know the standards for naming classes. The change to AnnotationBinder is minor and is delineated by '//dwsjoquist//' comment lines. Usage: @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL) @JoinColumn(name = "id") @CollectionTypeInfo(name = "examples.MyUserCollectionType") public List<ExampleAttribute> getExampleAttributes() { -- 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

15 years, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3365) SchemaUpdate still fails if conflicting table is visible in another user's tablespace

by John Wood (JIRA)

SchemaUpdate still fails if conflicting table is visible in another user's tablespace ------------------------------------------------------------------------------------- Key: HHH-3365 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3365 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.3.0.CR1, 3.2.6, 3.1 Reporter: John Wood Priority: Minor This issue is a duplicate of HHH-2208. Despite what that other issue states, this doesn't seem to be fixed. This issue still seems to a problem for us when using the SchemaUpdate tool to auto-update our tables (in Oracle). We've tried this using the following hibernate versions: 3.1, 3.2.6ga, 3.3.0.CR1 In every case the bug still happens: the schema update tool tries to update a table called "JOB", finds a table in someone else's schema (which happens to have been made public), and then gets confused. It will either try to update the other user's JOB table, or (in our case), fails because it (quite rightly) doesn't have permissions to change the other user's table. Here is how to reproduce: 1) Create your main DB user as normal (user1) 2) Create another user on the Oracle same database (user2) 3) On user2 create a new table which conflicts with a table in your generated DB ("job"). 4) Make this new table visible to user1. One way of doing this is to give "insert" privildeges to "public": grant insert on user2.job to public 5) Run the schema update tool for user1. This will fail: it tries to update the table in user2's schema (tablespace), and doesn't have permissions. Note that this issue only occurs when the conflicting table is visible to user1: if the table was hidden (i.e. user1 had no visibility of the conflicting table), we would be OK. It seems to me that either A) there is some confusion about when this issue was fixed, or B) this is a different issue to HHH-2208 -- 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

15 years, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3432) query.uniqueResult() potentially generates out of memory by calling list()

by Emmanuel Bernard (JIRA)

query.uniqueResult() potentially generates out of memory by calling list() -------------------------------------------------------------------------- Key: HHH-3432 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3432 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.3.0.CR2, 3.2.6 Reporter: Emmanuel Bernard calling list() while the user expects a single result has potential major flow: it's easy to trigger an out of memory situation where nobody would expect it... like getSingleResult("select CURRENT_TIME from AN_ENTITY_CONTAINING_ZILLIONS_OF_RECORDS") ; (and it is also a performance problem when it doesn't trigger the out of heap space... and a design issue: why fetching something the caller is not asking for ? with all the consequences on the cache...) fix: Something like that if (maxResults != 1) query.setMaxResults( 2 ); //avoid OOME if the list is huge List result = query.list(); if ( maxResults != -1 ) query.setMaxResults( maxResults ); //put back the original value -- 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

15 years, 6 months

3
3
0 / 0

[Hibernate-JIRA] Created: (EJB-365) Can't execute query

by Radosław Smogura (JIRA)

Can't execute query ------------------- Key: EJB-365 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-365 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.3.2.GA Environment: Hibernate 3.2.6 PostrgreSQL 8.0.13 Glassfish Reporter: Radosław Smogura Priority: Critical Execution followed named query with followed entity @Entity @NamedQuery(name="Foo.test", query="SELECT f FROM Foo f WHERE ((:bool IS NULL) OR (f.bool = :bool)) ") public class Foo implements Serializable{ @Id int id; boolean bool; public boolean isBool() { return bool; } public void setBool(boolean bool) { this.bool = bool; } public int getId() { return id; } public void setId(int id) { this.id = id; } } and parameter bool = null causes PostgreSQL error ERROR: operator does not exist: boolean = bytea -- 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

15 years, 6 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-303) Full review of reference documentation

by Hardy Ferentschik (JIRA)

Full review of reference documentation -------------------------------------- Key: HSEARCH-303 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-303 Project: Hibernate Search Issue Type: Task Components: documentation Reporter: Hardy Ferentschik Fix For: 3.1.0 We need to review the reference documentation and make sure that all the latest changes are properly refletcted. -- 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

15 years, 6 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-298) Warn for dangerous IndexWriter settings

by Sanne Grinovero (JIRA)

Warn for dangerous IndexWriter settings --------------------------------------- Key: HSEARCH-298 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-298 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.1.0.Beta2 Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial Fix For: 3.1.0.CR1 Usually we let the user set all IndexWriter tuning settings in a different way in "batch" mode or in "transaction" mode. MAX_FIELD_LENGTH and USE_COMPOUND_FILE are actually not impacting only performance but also how and what gets indexed, so for MAX_FIELD_LENGTH we need to log a warning (because it sounds really wrong but someone may like it), and throw an exception for USE_COMPOUND_FILE (because this would be dangerous). -- 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

15 years, 6 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HHH-3422) Oracle error: ORA-01754: a table may contain only one column of type LONG

by Martin Vařecha (JIRA)

Oracle error: ORA-01754: a table may contain only one column of type LONG ------------------------------------------------------------------------- Key: HHH-3422 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3422 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: Oracle 10g express edition release 10.2.0; Hibernate 3.2.6 GA; org.hibernate.dialect.Oracle10gDialect Reporter: Martin Vařecha I get this error "ORA-01754: a table may contain only one column of type LONG" during creating tables, because I have JPA bean with these two fields: @Column(name="text_content", length=16000) private String textContent; @Column(name="html_content", length=32000) private String htmlContent; For these huge text types column of long type is used and oracle doesn't allow more then one long in the table. -- 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

15 years, 7 months

3
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-73) Rename ConstraintViolation.getBeanClass() to CV. getRootClass() or simply remove it

by Emmanuel Bernard (JIRA)

Rename ConstraintViolation.getBeanClass() to CV. getRootClass() or simply remove it ----------------------------------------------------------------------------------- Key: BVAL-73 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-73 Project: Bean Validation Issue Type: Improvement Components: spec-general Reporter: Emmanuel Bernard -- 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

15 years, 7 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-221) Get Lucene Analyzer runtime (indexing)

by Kenneth Christensen (JIRA)

Get Lucene Analyzer runtime (indexing) -------------------------------------- Key: HSEARCH-221 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-221 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.0.1.GA Reporter: Kenneth Christensen Attachments: AddLuceneWork.java, DocumentBuilder.java, Flyer.java, LuceneWorker.java, TestBean.java I'm writing a multi-language application and I have choose to use Hibernate Search. But it looks like Hibernate Search have some limitations in multi-language applications. I need to use the SnowballAnalyzer and create the instance at runtime because I only know the language at runtime. It really looks like Hibernate Search don't support runtime created analyzers for entity instances. I have extended Hibernate Search to support the above issue - maybe you could include the code in Hibernate Search or implement something similarly. I really need this feature/improvement :-) Please see attached files. Flyer - Entity used in test TestBean - SessionBean used in test org.hibernate.search.backend.impl.lucene.LuceneWorker - Added code to support entity instance analyzer, see performWork(AddLuceneWork work, DirectoryProvider provider) and add(Class entity, Serializable id, Document document, DirectoryProvider provider, Analyzer analyzer). org.hibernate.search.backend.AddLuceneWork - Added code to support analyzer. org.hibernate.search.engine.DocumentBuilder - Added code to support entity instance analyzer, see addWorkToQueue(Class entityClass, T entity, Serializable id, WorkType workType, List<LuceneWork> queue, SearchFactoryImplementor searchFactoryImplementor). -- 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

15 years, 7 months

5
41
0 / 0

[Hibernate-JIRA] Created: (BVAL-76) Expose the raw message to ConstraintViolation

by Emmanuel Bernard (JIRA)

Expose the raw message to ConstraintViolation --------------------------------------------- Key: BVAL-76 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-76 Project: Bean Validation Issue Type: New Feature Components: spec-general Reporter: Emmanuel Bernard Fix For: 1.0 public draft -- 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

15 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 2008