December 2008 - hibernate-issues - Jboss List Archives

[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, 5 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-319) Database keyword in model SnowStorm causes failure

by Juraci Paixao Krohling (JIRA)

Database keyword in model SnowStorm causes failure -------------------------------------------------- Key: HSEARCH-319 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-319 Project: Hibernate Search Issue Type: Bug Environment: Test cases which uses SnowStorm model, running on Oracle (9i or 10g) Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: SnowStorm.diff The model uses a property named "date", which is a reserved keyword for Oracle. The attached patch adds a @Column annotation to it, specifying the table name as "xdate". It can be applied to both Branch_3_0_1_GA_CP and trunk. -- 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, 5 months

1
1
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, 5 months

3
9
0 / 0

[Hibernate-JIRA] Commented: (HHH-1930) QuerySyntaxException "with-clause expressions did not reference from-clause element to which the with-clause was associated"

by Mike Ressler (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1930?page=c... ] Mike Ressler commented on HHH-1930: ----------------------------------- Spoke too soon. The generated SQL doesn't include the with clause at all, all my data was messed up: HQL: select person, count(data.referenceMe) from model.DataAboutPerson as data right join data.whoImAllAbout as person with (data.referenceMe like 'me%') SQL: select person1_.person as col_0_0_, count(dataaboutp0_.referenceme) as col_1_0_, person1_.person as person1_, person1_.name as name1_ from dataaboutperson dataaboutp0_ right outer join people person1_ on dataaboutp0_.person=person1_.person The ON keyword exists, but the "like 'me%'" information is lost. Looks like I'll need to dig deeper into the SQL generation code to find where the info is lost. The log4j debug logs don't seem to be leading me in any particular direction. Anyone watching this bug that can point me in the right direction in the SQL generation code? Or anyone that might know the underlying reason why this isn't supported already? > QuerySyntaxException "with-clause expressions did not reference from-clause element to which the with-clause was associated" > ---------------------------------------------------------------------------------------------------------------------------- > > Key: HHH-1930 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1930 > Project: Hibernate Core > Issue Type: Bug > Components: query-hql > Affects Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2, 3.2.0.cr3 > Reporter: Manfred Geiler > Attachments: HibernateTestCase.zip > > > In Version 3.1.2 the following "EventManager" HQL query worked fine: > select p from Person p join p.emailAddresses as email with email = 'xyz' > and produced an SQL query like this: > select person0_.PERSON_ID as PERSON1_2_, person0_.age as age2_, person0_.firstname as firstname2_, person0_.lastname as lastname2_ > from PERSON person0_ > inner join PERSON_EMAIL_ADDR emailaddre1_ > on person0_.PERSON_ID=emailaddre1_.PERSON_ID and (emailaddre1_.EMAIL_ADDR='xyz') > From Version 3.1.3 on this HQL throws the following QuerySyntaxException: > "with-clause expressions did not reference from-clause element to which the with-clause was associated" -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1930) QuerySyntaxException "with-clause expressions did not reference from-clause element to which the with-clause was associated"

by Antonio Juarez (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1930?page=c... ] Antonio Juarez commented on HHH-1930: ------------------------------------- I don't think we can just comment the lines out - there should be some kind of restriction on this WITH part of the query. It doesn't need to reference the right-hand side, but I believe it should reference either the right-hand or the left-hand side of the query, and that does call for some validation. Maybe the if() condition could be replaced by something like: if ( referencedFromElement != fromElement && referencedFromElement!=leftHandSideFromElement) { throw new InvalidWithClausException(......); } IMO > QuerySyntaxException "with-clause expressions did not reference from-clause element to which the with-clause was associated" > ---------------------------------------------------------------------------------------------------------------------------- > > Key: HHH-1930 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1930 > Project: Hibernate Core > Issue Type: Bug > Components: query-hql > Affects Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2, 3.2.0.cr3 > Reporter: Manfred Geiler > Attachments: HibernateTestCase.zip > > > In Version 3.1.2 the following "EventManager" HQL query worked fine: > select p from Person p join p.emailAddresses as email with email = 'xyz' > and produced an SQL query like this: > select person0_.PERSON_ID as PERSON1_2_, person0_.age as age2_, person0_.firstname as firstname2_, person0_.lastname as lastname2_ > from PERSON person0_ > inner join PERSON_EMAIL_ADDR emailaddre1_ > on person0_.PERSON_ID=emailaddre1_.PERSON_ID and (emailaddre1_.EMAIL_ADDR='xyz') > From Version 3.1.3 on this HQL throws the following QuerySyntaxException: > "with-clause expressions did not reference from-clause element to which the with-clause was associated" -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1930) QuerySyntaxException "with-clause expressions did not reference from-clause element to which the with-clause was associated"

by Mike Ressler (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1930?page=c... ] Mike Ressler commented on HHH-1930: ----------------------------------- Commented out HqlSqlWalker.handleWithFragment lines 362-364 in the trunk version this evening and the TestCase passes. Since the version in trunk will change, the three lines I commented out were: if ( referencedFromElement != fromElement ) { throw new InvalidWithClauseException( "with-clause expressions did not reference from-clause element to which the with-clause was associated" ); } If this is an acceptable fix for this bug, I'll create a patch file to apply to trunk. Let me know if you'd like me to do anything else to verify this fix. Other Notes: It seems like the with clause should be able to refer to either part of the referenced "from" element. I should be able to limit the sql results based on attributes of either part of a join statement, not just the right hand side of the join. So this begs the question, why is this check necessary? I'm sure I'm missing something here, any comments would be appreciated. > QuerySyntaxException "with-clause expressions did not reference from-clause element to which the with-clause was associated" > ---------------------------------------------------------------------------------------------------------------------------- > > Key: HHH-1930 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1930 > Project: Hibernate Core > Issue Type: Bug > Components: query-hql > Affects Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2, 3.2.0.cr3 > Reporter: Manfred Geiler > Attachments: HibernateTestCase.zip > > > In Version 3.1.2 the following "EventManager" HQL query worked fine: > select p from Person p join p.emailAddresses as email with email = 'xyz' > and produced an SQL query like this: > select person0_.PERSON_ID as PERSON1_2_, person0_.age as age2_, person0_.firstname as firstname2_, person0_.lastname as lastname2_ > from PERSON person0_ > inner join PERSON_EMAIL_ADDR emailaddre1_ > on person0_.PERSON_ID=emailaddre1_.PERSON_ID and (emailaddre1_.EMAIL_ADDR='xyz') > From Version 3.1.3 on this HQL throws the following QuerySyntaxException: > "with-clause expressions did not reference from-clause element to which the with-clause was associated" -- 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, 5 months

1
0
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, 5 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-317) Bug in annotations is affecting HSearch test case

by Juraci Paixao Krohling (JIRA)

Bug in annotations is affecting HSearch test case ------------------------------------------------- Key: HSEARCH-317 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-317 Project: Hibernate Search Issue Type: Patch Reporter: Juraci Paixao Krohling Attachments: Product.diff Bug JBPAPP-1071 in Annotations is affecting test cases which uses org.hibernate.search.test.embedded.Product . Workaround is to manually mark the column CUST_NAME as nullable=false. -- 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, 5 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-315) ReaderPerfTestCase uses a too high value for suspectCharge property

by Juraci Paixao Krohling (JIRA)

ReaderPerfTestCase uses a too high value for suspectCharge property ------------------------------------------------------------------- Key: HSEARCH-315 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-315 Project: Hibernate Search Issue Type: Patch Environment: All databases, except HSQLDB Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: ReaderPerfTestCase.diff Test case ReaderPerfTestCase sets the property suspectCharge to a value too high for the usual varchar(255), affecting most of the RDMBS's. Solution is to crop the value, to contain at most 255 chars. -- 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, 5 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3630) When querying for component, Map collections inside components not loaded

by Gino Miceli (JIRA)

When querying for component, Map collections inside components not loaded -------------------------------------------------------------------------- Key: HHH-3630 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3630 Project: Hibernate Core Issue Type: Bug Environment: 3.2.6-GA, Oracle and HSQLDB, JDK 1.5 Reporter: Gino Miceli Attachments: hibernate-test.zip Given the following mapping: <code> <class name="Car" table="CAR"> <id name="id" column="ID" type="long"> <generator class="native"/> </id> <property name="make" column="MAKE"/> <property name="model" column="MODEL"/> <component name="engine" class="Engine"> <property name="make" column="ENGINE_MAKE"/> <property name="model" column="ENGINE_MODEL"/> <map name="mountParts" table="ENGINE_MOUNT"> <key column="CAR_ID"/> <map-key column="PART_NAME" type="string" /> <element column="PART" type="string" /> </map> </component> </class> </code> We are able to get the entire Car object in HQL like so: <code> select car from Car car where car.id=1 </code> This generates the following SQL: <code> select mountparts0_.CAR_ID as CAR1_0_, mountparts0_.PART as PART0_, mountparts0_.PART_NAME as PART3_0_ from ENGINE_MOUNT mountparts0_ where mountparts0_.CAR_ID=? </code> In this case, the map contained in the 'engine' component is loaded correctly. If we query the component property directly, however: <code> select car.engine from Car car where car.id=1 </code> Instances of Engine are returned, however the contained map is null. Looking at the SQL, it appears not attempt is made to load the inner map property: <code> select car0_.ENGINE_MAKE as col_0_0_, car0_.ENGINE_MODEL as col_0_1_ from CAR car0_ where car0_.ID=1 </code> Anyone?! -- 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, 5 months

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