May 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HBX-940) Allow select all in the HQL Query Editor

by Peter Mularien (JIRA)

Allow select all in the HQL Query Editor ---------------------------------------- Key: HBX-940 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-940 Project: Hibernate Tools Issue Type: Improvement Components: eclipse Affects Versions: 3.2beta9 Environment: HHH 3.2, Oracle 10, Eclipse 3.2.2 Reporter: Peter Mularien Priority: Minor It would be wonderful if the Eclipse plugin could support Select All (Ctrl-A) in the HQL editor. I often use the HQL editor for prototyping queries, and then select all - paste into my Java class. Thanks for the consideration. -- 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

3
2
0 / 0

[Hibernate-JIRA] Resolved: (HBX-649) Alphabetize pojos in Hibernate Configuration view in Eclipse

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-649?page=co... ] Max Rydahl Andersen resolved HBX-649. ------------------------------------- Resolution: Fixed Fix Version/s: 3.2.1 fixed a while ago > Alphabetize pojos in Hibernate Configuration view in Eclipse > ------------------------------------------------------------ > > Key: HBX-649 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-649 > Project: Hibernate Tools > Issue Type: Improvement > Components: eclipse > Affects Versions: 3.1beta4 > Environment: Windows 2000 > Reporter: Jim Bethancourt > Priority: Trivial > Fix For: 3.2.1 > > > Would it be possible to alphebetize the pojos in the Hibernate Configuration view via a button (like the one available Eclipse's Outline view)? I think folks would find it handy. > Thanks, > Jim -- 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

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3263) Postgres dialect quoting defect

by Stephan Fuhrmann (JIRA)

Postgres dialect quoting defect ------------------------------- Key: HHH-3263 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3263 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: hibernate-3.2.6.ga, postgres 7.4.19, jdbc-driver postgresql-8.3-603.jdbc4.jar Reporter: Stephan Fuhrmann Priority: Critical Attachments: hibernate.cfg.xml Special characters do not seem to be quoted / escaped. This makes the database parser throw an exception if it encounters such a unescaped String: org.hibernate.exception.DataException: could not insert collection: [org.fstool.io.fs.UserInfoAttributes.attributes#205] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:77) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.persister.collection.AbstractCollectionPersister.recreate(AbstractCollectionPersister.java:1183) at org.hibernate.action.CollectionRecreateAction.execute(CollectionRecreateAction.java:39) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:171) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:301) at $Proxy0.flush(Unknown Source) ... Caused by: java.sql.BatchUpdateException: Batch-Eintrag 6 insert into attributes (id, property_name, property_value) values (205, 9, (¯`'<95>.?<95> a <95>?. <95>'?¯)) wurde abgebrochen. Rufen Sie 'getNextException' auf, um die Ursache zu erfahren. at org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError(AbstractJdbc2Statement.java:2537) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1328) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:351) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2674) at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48) at org.hibernate.jdbc.BatchingBatcher.addToBatch(BatchingBatcher.java:34) at org.hibernate.persister.collection.AbstractCollectionPersister.recreate(AbstractCollectionPersister.java:1146) ... 22 more The offending character seems to be ISO 8859-1 0xb4 (ACUTE ACCENT). The map file excerpt for this: ... <map name="attributes"> <key column="id"/> <index-many-to-many column="property_name" class="org.fstool.io.fs.AttributeKey"/> <element column="property_value" type="string"/>  </map> ... The application doesn't need to care about escaping because Hibernate does the job of O/R-mapping. The problem does NOT exist for the DerbyDialect - this works fine! Note: If characters get passed to the DB unescaped this is a security risk opening a hole for SQL injection! Therefore I marked this problem critical. -- 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

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3284) TimeZoneType takes too much space in 2nd level cache

by Yossi Tamari (JIRA)

TimeZoneType takes too much space in 2nd level cache ---------------------------------------------------- Key: HHH-3284 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3284 Project: Hibernate3 Issue Type: Bug Components: caching (L2) Affects Versions: 3.2.6 Reporter: Yossi Tamari Priority: Minor TimeZoneType does not override the assemble/disassemble methods, and as a result the whole sun.util.calendar.ZoneInfo object is stored in the second level cache, and if using a distributed copying cache, the whole structure is serialized and sent across the network. This is very inefficient since the ZoneInfo contains a number of arrays, and for some timezones (like europe/london) some of the arrays (specifically transitions, an array of long) have over a hundred elements. Considering that the objects are stored in the DB as string IDs, simply overiding disassemble to return this string, and overinding assemble to return TimeZone.getTimeZone(value) would achieve huge memory (and potentialy network) savings, at the cost of object creation. -- 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

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3282) DB2Dialect should report supportsLobValueChangePropogation() == false

by Steve Ebersole (JIRA)

DB2Dialect should report supportsLobValueChangePropogation() == false --------------------------------------------------------------------- Key: HHH-3282 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3282 Project: Hibernate3 Issue Type: Bug Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.2.x, 3.3.0.CR2 Currently, org.hibernate.dialect.DB2Dialect does not override the supportsLobValueChangePropogation() method. The base Dialect defaults that to true. In my tests against a 9.1.3a server with the IBM drivers, the changing of the locator value was certainly not propagated. -- 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

1
1
0 / 0

[Hibernate-JIRA] Updated: (HBX-676) Use HQL Lexer in color coding

by Dmitry Geraskov (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-676?page=co... ] Dmitry Geraskov updated HBX-676: -------------------------------- Attachment: hql_keywords_patch.txt Use HQLBaseLexer to find hql/sql keywords(added many unused in previous version: avg, summ, ascending ...), use WordRule to find hql/sql functions. > Use HQL Lexer in color coding > ----------------------------- > > Key: HBX-676 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-676 > Project: Hibernate Tools > Issue Type: Improvement > Components: eclipse > Reporter: Max Rydahl Andersen > Fix For: 3.2LATER > > Attachments: hql_keywords_patch.txt, HQLCodeScanner_patch_HBX-676.txt, HQLCodeScanner_patch_HBX-676.txt, HQLLexerRule_patch_HBX-676.txt > > -- 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

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3281) Instrumentation does not work with components

by Alexey Romanchuk (JIRA)

Instrumentation does not work with components --------------------------------------------- Key: HHH-3281 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3281 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6 Reporter: Alexey Romanchuk Assume that we have class (A) with component (B) that refers to another class (C). When I map C as field of B and set lazy="no-proxy" and pass all classes (A, B, C) to instrumentation C still returned from B as proxy. -- 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

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1697) OracleDialect fails to recognize sequence accessible through syonyms when validating schema

by Diego Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1697?page=c... ] Diego Plentz updated HHH-1697: ------------------------------ Assignee: Diego Plentz Affects Version/s: 3.3.0.CR1 Component/s: core > OracleDialect fails to recognize sequence accessible through syonyms when validating schema > ------------------------------------------------------------------------------------------- > > Key: HHH-1697 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1697 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.3.0.CR1 > Environment: Hibernate 3.1.2, Hibernate 3.1.3 Oracle 10g > Reporter: Bjørn Bjerkeli > Assignee: Diego Plentz > Priority: Minor > Attachments: Oracle9Dialect.java > > > The Dialect implementations in OracleDialect and Oracle9Dialect fails to recognize sequences upon validation when they are accesssed through synonyms > because the user_sequences table will not create when the sequence is acced through a synonym. This is needed when using hibernate.hbm2ddl.auto=validate > which is a very useful feature. > Thus sequences returned by: > public String getQuerySequencesString() { > return "select sequence_name from user_sequences"; > } > will mot identify sequences accessible using a synonym. > By using this implementation: > public String getQuerySequencesString() { > return "select sequence_name from user_sequences " + > "union " + > "select synonym_name from user_synonyms us " + > "where exists (select 1 from all_objects ao where object_type='SEQUENCE' and " + > "us.table_name = ao.object_name)"; > } > orale will also return sequences acccessible though synonyms. -- 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

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1697) OracleDialect fails to recognize sequence accessible through syonyms when validating schema

by Diego Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1697?page=c... ] Diego Plentz commented on HHH-1697: ----------------------------------- This sequence works with at least 8i. Sources: http://www.oracle.com/pls/db102/ http://www.oracle.com/pls/db111/ http://www.oracle.com/pls/tahiti/ http://www.oracle.com/pls/db92/ > OracleDialect fails to recognize sequence accessible through syonyms when validating schema > ------------------------------------------------------------------------------------------- > > Key: HHH-1697 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1697 > Project: Hibernate3 > Issue Type: Bug > Environment: Hibernate 3.1.2, Hibernate 3.1.3 Oracle 10g > Reporter: Bjørn Bjerkeli > Priority: Minor > Attachments: Oracle9Dialect.java > > > The Dialect implementations in OracleDialect and Oracle9Dialect fails to recognize sequences upon validation when they are accesssed through synonyms > because the user_sequences table will not create when the sequence is acced through a synonym. This is needed when using hibernate.hbm2ddl.auto=validate > which is a very useful feature. > Thus sequences returned by: > public String getQuerySequencesString() { > return "select sequence_name from user_sequences"; > } > will mot identify sequences accessible using a synonym. > By using this implementation: > public String getQuerySequencesString() { > return "select sequence_name from user_sequences " + > "union " + > "select synonym_name from user_synonyms us " + > "where exists (select 1 from all_objects ao where object_type='SEQUENCE' and " + > "us.table_name = ao.object_name)"; > } > orale will also return sequences acccessible though synonyms. -- 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

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1697) OracleDialect fails to recognize sequence accessible through syonyms when validating schema

by Diego Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1697?page=c... ] Diego Plentz commented on HHH-1697: ----------------------------------- The first improvement that we will do is change from user_sequences view to all_sequences view since "ALL_SEQUENCES describes all sequences accessible to the user.". > OracleDialect fails to recognize sequence accessible through syonyms when validating schema > ------------------------------------------------------------------------------------------- > > Key: HHH-1697 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1697 > Project: Hibernate3 > Issue Type: Bug > Environment: Hibernate 3.1.2, Hibernate 3.1.3 Oracle 10g > Reporter: Bjørn Bjerkeli > Priority: Minor > Attachments: Oracle9Dialect.java > > > The Dialect implementations in OracleDialect and Oracle9Dialect fails to recognize sequences upon validation when they are accesssed through synonyms > because the user_sequences table will not create when the sequence is acced through a synonym. This is needed when using hibernate.hbm2ddl.auto=validate > which is a very useful feature. > Thus sequences returned by: > public String getQuerySequencesString() { > return "select sequence_name from user_sequences"; > } > will mot identify sequences accessible using a synonym. > By using this implementation: > public String getQuerySequencesString() { > return "select sequence_name from user_sequences " + > "union " + > "select synonym_name from user_synonyms us " + > "where exists (select 1 from all_objects ao where object_type='SEQUENCE' and " + > "us.table_name = ao.object_name)"; > } > orale will also return sequences acccessible though synonyms. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2008