hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-280) support formula properties in where clause

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sat, 29 Nov 2003 12:50 AM

Done.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-280


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-280
    Summary: support formula properties in where clause
       Type: New Feature

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 rc1

   Assignee: Gavin King
   Reporter: Tim Schafer

    Created: Thu, 21 Aug 2003 6:23 PM
    Updated: Sat, 29 Nov 2003 12:50 AM

Description:
Be able to use the property in an HQL where clause
and have the formula inserted into the resulting SQL


---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-507) session.save() does not create records in child table for composite ids

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Fri, 28 Nov 2003 7:27 PM

PLease redirect this issue to the user forum, and provide sufficient info (esp. mapping documents). This is certainly not a bug in Hibernate (we have a test suite).
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-507


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-507
    Summary: session.save() does not create records in child table for composite ids
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
   Versions:
             2.1 beta 4

   Assignee: 
   Reporter: Mikheil Kapanadze

    Created: Fri, 28 Nov 2003 8:54 AM
    Updated: Fri, 28 Nov 2003 7:27 PM

Description:
We have 2 persistent object, Highlight and HighlightLinks. Highlight object has one-to-many association to HighlightLinks with cascade="all", while the second one has composite id

<composite-id>
  <key-many-to-one name="highlight" class="Highlight" column="HIGHLIGHT_ID"/>
  <key-property name="offset" column="OFFSET" type="int"/>
</composite-id>

HighlightLinks object implements java.io.Serializable interface and equals()/hashCode() methods.

The code looks like:

Highlight highlight = new Highlight();
//Some setX() methods on highlight

highlight.setLinks(new HashSet());
HighlightLinks link = new HighlightLinks();

link.setOffset(linkItem.getIndex());
link.setHighlight(highlight);
//Some other setX() methods on link

highlight.getLinks().add(link);

//Some stuff here

session.save(highlight);

After this, the new record appears in HIGHLIGHT table, while HIGHLIGHT_LINK is empty.

As we can see from logs (show_sql is turned on), Hibernate is trying to update HIGHLIGHT_LINK table instead of inserting there.

We checked this issue on Hibernate 2.0.1 - it works (initially code was developed for this version). We found this issue in 2.1 beta 4.

We also checked out the latest code from CVS and the problem seems to still exist.

Thanks,
Mikheil


---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-507) session.save() does not create records in child table for composite ids

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Fri, 28 Nov 2003 11:23 AM
       Body:
We have a unittest for that one that does work ;)
so please provide testcase that fails.


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-507


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-507
    Summary: session.save() does not create records in child table for composite ids
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.1 beta 4

   Assignee: 
   Reporter: Mikheil Kapanadze

    Created: Fri, 28 Nov 2003 8:54 AM
    Updated: Fri, 28 Nov 2003 11:23 AM

Description:
We have 2 persistent object, Highlight and HighlightLinks. Highlight object has one-to-many association to HighlightLinks with cascade="all", while the second one has composite id

<composite-id>
  <key-many-to-one name="highlight" class="Highlight" column="HIGHLIGHT_ID"/>
  <key-property name="offset" column="OFFSET" type="int"/>
</composite-id>

HighlightLinks object implements java.io.Serializable interface and equals()/hashCode() methods.

The code looks like:

Highlight highlight = new Highlight();
//Some setX() methods on highlight

highlight.setLinks(new HashSet());
HighlightLinks link = new HighlightLinks();

link.setOffset(linkItem.getIndex());
link.setHighlight(highlight);
//Some other setX() methods on link

highlight.getLinks().add(link);

//Some stuff here

session.save(highlight);

After this, the new record appears in HIGHLIGHT table, while HIGHLIGHT_LINK is empty.

As we can see from logs (show_sql is turned on), Hibernate is trying to update HIGHLIGHT_LINK table instead of inserting there.

We checked this issue on Hibernate 2.0.1 - it works (initially code was developed for this version). We found this issue in 2.1 beta 4.

We also checked out the latest code from CVS and the problem seems to still exist.

Thanks,
Mikheil


---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-506) Non-deterministic? failure of generated proxies

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Panagiotis Louridas
    Created: Fri, 28 Nov 2003 9:34 AM
       Body:
Great.

If you happen by Athens, let me buy you a beer.

Best Regards,

Panos.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-506


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-506
    Summary: Non-deterministic? failure of generated proxies
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
   Fix Fors:
             2.1 rc1
   Versions:
             2.0.3

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Fri, 28 Nov 2003 3:59 AM
    Updated: Fri, 28 Nov 2003 9:34 AM
Environment: redhat linux 9, j2se 1.4.2 (build 1.4.2-b28), postgres, hibernate 2.0.3

Description:
Suppose we have a class hierarchy A <- B, A <- C. Both class B and C have a method getX(). Suppose, moreover, that we have a class R that contains a reference to A.

If we do a query on class R and then a query on class B or C, we *sometimes* get a ClassCastException for the generated proxy when we try to call getX(). In my environment, the same test case succeeds or fails upon repeated execution.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-506) Non-deterministic? failure of generated proxies

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Fri, 28 Nov 2003 9:21 AM
       Body:
Yeah - i'll go change the wording to "I get an exception when running junit" or something like that instead.

Don't like the "hibernate and junit" as a problem in one sentence - since the culprit ain't hibernate, but mostly junit and the jakarta libs that messes things up ;)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-506


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-506
    Summary: Non-deterministic? failure of generated proxies
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
   Fix Fors:
             2.1 rc1
   Versions:
             2.0.3

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Fri, 28 Nov 2003 3:59 AM
    Updated: Fri, 28 Nov 2003 9:21 AM
Environment: redhat linux 9, j2se 1.4.2 (build 1.4.2-b28), postgres, hibernate 2.0.3

Description:
Suppose we have a class hierarchy A <- B, A <- C. Both class B and C have a method getX(). Suppose, moreover, that we have a class R that contains a reference to A.

If we do a query on class R and then a query on class B or C, we *sometimes* get a ClassCastException for the generated proxy when we try to call getX(). In my environment, the same test case succeeds or fails upon repeated execution.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-507) session.save() does not create records in child table for composite ids

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-507


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-507
    Summary: session.save() does not create records in child table for composite ids
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.1 beta 4

   Assignee: 
   Reporter: Mikheil Kapanadze

    Created: Fri, 28 Nov 2003 8:54 AM
    Updated: Fri, 28 Nov 2003 8:54 AM

Description:
We have 2 persistent object, Highlight and HighlightLinks. Highlight object has one-to-many association to HighlightLinks with cascade="all", while the second one has composite id

<composite-id>
  <key-many-to-one name="highlight" class="Highlight" column="HIGHLIGHT_ID"/>
  <key-property name="offset" column="OFFSET" type="int"/>
</composite-id>

HighlightLinks object implements java.io.Serializable interface and equals()/hashCode() methods.

The code looks like:

Highlight highlight = new Highlight();
//Some setX() methods on highlight

highlight.setLinks(new HashSet());
HighlightLinks link = new HighlightLinks();

link.setOffset(linkItem.getIndex());
link.setHighlight(highlight);
//Some other setX() methods on link

highlight.getLinks().add(link);

//Some stuff here

session.save(highlight);

After this, the new record appears in HIGHLIGHT table, while HIGHLIGHT_LINK is empty.

As we can see from logs (show_sql is turned on), Hibernate is trying to update HIGHLIGHT_LINK table instead of inserting there.

We checked this issue on Hibernate 2.0.1 - it works (initially code was developed for this version). We found this issue in 2.1 beta 4.

We also checked out the latest code from CVS and the problem seems to still exist.

Thanks,
Mikheil


---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-506) Non-deterministic? failure of generated proxies

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Panagiotis Louridas
    Created: Fri, 28 Nov 2003 8:46 AM
       Body:
I tried solution (2) and it works fine.

Thanks a lot Max, and sorry for taking up your time. You made at least a few people aroung here pack happy for the weekend. I really appreciate your excellent feedback.

In retrospect it seems amazing that, although reflection would be mangled, it has been several months that junit has been used in this way without hibernate carping...

Just a suggestion:

I had browsed the FAQs and I had seen the item; however, I had been getting no ClassCastException; even now, I get a LogConfigurationException. To be sure, I might have investigated anyway. Still, perhaps others would be saved from trouble if the heading in that FAQ were changed to something like: "using hibernate and junit"? It seems to me that the advice applies *anyway*, ClassCastException or not.

Best Regards,

Thanks again,

Panos.

 
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-506


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-506
    Summary: Non-deterministic? failure of generated proxies
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
   Fix Fors:
             2.1 rc1
   Versions:
             2.0.3

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Fri, 28 Nov 2003 3:59 AM
    Updated: Fri, 28 Nov 2003 8:46 AM
Environment: redhat linux 9, j2se 1.4.2 (build 1.4.2-b28), postgres, hibernate 2.0.3

Description:
Suppose we have a class hierarchy A <- B, A <- C. Both class B and C have a method getX(). Suppose, moreover, that we have a class R that contains a reference to A.

If we do a query on class R and then a query on class B or C, we *sometimes* get a ClassCastException for the generated proxy when we try to call getX(). In my environment, the same test case succeeds or fails upon repeated execution.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-506) Non-deterministic? failure of generated proxies

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Fri, 28 Nov 2003 8:11 AM
       Body:
From the FAQ at http://www.hibernate.org/119.html:

Unit Testing
I get a ClassCastException when I try to call Hibernate from inside JUnit.

Fix 1 (Gareth Cronin)

Anyone using log4j/commons and JUnit should change the junit/runner/excluded.properties file inside junit.jar to look like this (it will get rid of all annoying Jakarta issues): 

excluded.0=sun.* 
excluded.1=com.sun.* 
excluded.2=org.omg.* 
excluded.3=javax.* 
excluded.4=sunw.* 
excluded.5=java.* 
excluded.6=org.xml.sax.* 
excluded.7=org.w3c.dom.* 
excluded.8=org.apache.log4j.* 
excluded.9=org.apache.commons.*

Fix 2 (Eric Everman)

Another fix for this is to turn off class reloading in JUnit.



Your problem is commons-log, not hibernate.
And your solution about shortcutting the threadcontextclassloader will for sure mess up every library that uses reflection.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-506


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-506
    Summary: Non-deterministic? failure of generated proxies
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
   Fix Fors:
             2.1 rc1
   Versions:
             2.0.3

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Fri, 28 Nov 2003 3:59 AM
    Updated: Fri, 28 Nov 2003 8:11 AM
Environment: redhat linux 9, j2se 1.4.2 (build 1.4.2-b28), postgres, hibernate 2.0.3

Description:
Suppose we have a class hierarchy A <- B, A <- C. Both class B and C have a method getX(). Suppose, moreover, that we have a class R that contains a reference to A.

If we do a query on class R and then a query on class B or C, we *sometimes* get a ClassCastException for the generated proxy when we try to call getX(). In my environment, the same test case succeeds or fails upon repeated execution.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-506) Non-deterministic? failure of generated proxies

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Panagiotis Louridas
    Created: Fri, 28 Nov 2003 7:54 AM
       Body:
Running ant -v confirms that, apart from hibernate2.jar and all the jars in hibernate/lib, the only other jars included are the postgres drivem the ant jars and the j2sdk tools. The only related dependency I see there is the one between hibernate/lib/junit.jar and hibernate/lib/commons-logging.jar

Here is the classpath as output from ant:
/home/panos/src/java/HibernateReport3/build/classes
/home/panos/src/java/HibernateReport3/src
/usr/local/hibernate-2.0/hibernate2.jar
/usr/local/hibernate-2.0/lib/commons-lang.jar
/usr/local/hibernate-2.0/lib/commons-logging.jar
/usr/local/hibernate-2.0/lib/dom4j.jar
/usr/local/hibernate-2.0/lib/junit.jar
/usr/share/pgsql/pg73jdbc3.jar
/usr/local/apache-ant-1.5.3-1/lib/xml-apis.jar
/usr/local/apache-ant-1.5.3-1/lib/xercesImpl.jar
/usr/local/apache-ant-1.5.3-1/lib/optional.jar
/usr/local/apache-ant-1.5.3-1/lib/ant.jar
/usr/java/j2sdk/lib/tools.jar

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-506


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-506
    Summary: Non-deterministic? failure of generated proxies
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
   Fix Fors:
             2.1 rc1
   Versions:
             2.0.3

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Fri, 28 Nov 2003 3:59 AM
    Updated: Fri, 28 Nov 2003 7:54 AM
Environment: redhat linux 9, j2se 1.4.2 (build 1.4.2-b28), postgres, hibernate 2.0.3

Description:
Suppose we have a class hierarchy A <- B, A <- C. Both class B and C have a method getX(). Suppose, moreover, that we have a class R that contains a reference to A.

If we do a query on class R and then a query on class B or C, we *sometimes* get a ClassCastException for the generated proxy when we try to call getX(). In my environment, the same test case succeeds or fails upon repeated execution.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-363) Constraint.java does not support CascadeConstraintsString

[<leg...@at...>]

The following comment has been added to this issue:

     Author: ron lussier
    Created: Fri, 28 Nov 2003 7:53 AM
       Body:
Okay, let me know when this has been addressed and I will test out the issue.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-363


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-363
    Summary: Constraint.java does not support CascadeConstraintsString
       Type: Bug

     Status: Reopened
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 rc1
   Versions:
             2.1 beta 3

   Assignee: Max Rydahl Andersen
   Reporter: ron lussier

    Created: Thu, 25 Sep 2003 1:38 PM
    Updated: Fri, 28 Nov 2003 7:53 AM
Environment: Mac OS X, Frontbase

Description:
In order to properly support SQL92, a change is required to allow the 'alter table ... drop constraint' statement to take a drop behavior.  This change affects net.sf.hibernate.mapping.Constraint.java, line 43.  I would like the line to read:

   return "alter table " + getTable().getQualifiedName(dialect) +
          " drop constraint " + getName() +
          dialect.getCascadeConstraintsString();

Frontbase (the dialect I contributed) requires either 'CASCADE' or 'RESTRICT' in a drop constraint clause.  (Frontbase is VERY SQL/92 standard, sometimes annoyingly.)  Isn't this what the dialect.getCascadeConstraintsString() property is for?  (The documentation for the property reads 'Completely optional cascading drop clause'.)

According to the documentation for SQL/92 (from http://www.contrib.andrew.cmu.edu/~shadow/sql/sql2bnf.aug92.txt), the syntax should be:

   <alter table statement> ::=
       ALTER TABLE <table name> <alter table action>

   <alter table action> ::=
         <add column definition>
       | <alter column definition>
       | <drop column definition>
       | <add table constraint definition>
       | <drop table constraint definition>

   <drop table constraint definition> ::=
       DROP CONSTRAINT <constraint name> <drop behavior>

   <drop behavior> ::= CASCADE | RESTRICT

The requirement of CASCADE or RESTRICT is also affirmed in "A Guide to the SQL Standard", Fourth Edition, on page 106, where the syntax is given as:

   base-table-alteration
      ::= ALTER TABLE base-table base-table-alteration-action

   base-table-alteration-action
      ::=   column-alteration-action
            | base-table-constraint-alteration-action

   base-table-constraint-alteration-action
      ::=    ADD base-table-constraint-definition
            | DROP CONSTRAINT constraint { RESTRICT | CASCADE }

On page 38 of the same volume, under 'Notation', the book states "Braces '{' and '}' are used to indicate that the material enclosed in those braces consists of a set of two or more items (separated by vertical bars) from which exactly one is to be chosen.

If you would prefer, I would be fine with creating a new, optional property of Dialect.java for this purpose, but I think that Hibernate needs something.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-506) Non-deterministic? failure of generated proxies

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Fri, 28 Nov 2003 7:29 AM
       Body:
That looks to me like some really messed up .jar dependencies!

I can run your tests just fine from eclipse.


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-506


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-506
    Summary: Non-deterministic? failure of generated proxies
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
   Fix Fors:
             2.1 rc1
   Versions:
             2.0.3

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Fri, 28 Nov 2003 3:59 AM
    Updated: Fri, 28 Nov 2003 7:29 AM
Environment: redhat linux 9, j2se 1.4.2 (build 1.4.2-b28), postgres, hibernate 2.0.3

Description:
Suppose we have a class hierarchy A <- B, A <- C. Both class B and C have a method getX(). Suppose, moreover, that we have a class R that contains a reference to A.

If we do a query on class R and then a query on class B or C, we *sometimes* get a ClassCastException for the generated proxy when we try to call getX(). In my environment, the same test case succeeds or fails upon repeated execution.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-506) Non-deterministic? failure of generated proxies

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Panagiotis Louridas
    Created: Fri, 28 Nov 2003 7:24 AM
       Body:
If I do remove these lines---I am running ant from the command line--- I cannot run the test at all, so I do need them. This is what I get for removing them:

[java] java.lang.ExceptionInInitializerError
     [java]     at ProxyTest$1.run(Unknown Source)
     [java]     at junit.swingui.TestRunner$16.run(TestRunner.java:623)
     [java] Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Jdk14Logger does not implement Log
     [java]     at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532)
     [java]     at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272)
     [java]     at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246)
     [java]     at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
     [java]     at net.sf.hibernate.cfg.Configuration.<clinit>(Configuration.java:86)
     [java]     ... 2 more
     [java] Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Jdk14Logger does not implement Log
     [java]     at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:416)
     [java]     at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525)
     [java]     ... 6 more
     [java] Caused by: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Jdk14Logger does not implement Log
     [java]     at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:412)
     [java]     ... 7 more

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-506


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-506
    Summary: Non-deterministic? failure of generated proxies
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
   Fix Fors:
             2.1 rc1
   Versions:
             2.0.3

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Fri, 28 Nov 2003 3:59 AM
    Updated: Fri, 28 Nov 2003 7:24 AM
Environment: redhat linux 9, j2se 1.4.2 (build 1.4.2-b28), postgres, hibernate 2.0.3

Description:
Suppose we have a class hierarchy A <- B, A <- C. Both class B and C have a method getX(). Suppose, moreover, that we have a class R that contains a reference to A.

If we do a query on class R and then a query on class B or C, we *sometimes* get a ClassCastException for the generated proxy when we try to call getX(). In my environment, the same test case succeeds or fails upon repeated execution.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-506) Non-deterministic? failure of generated proxies

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Max Rydahl Andersen
       Date: Fri, 28 Nov 2003 6:40 AM

You had the following line in your testcase:

// this makes the reload option of the JUnit GUI work
    Thread.currentThread()
                       .setContextClassLoader(getClass().getClassLoader());
		    
Removing those weird and nonsense (IMOH) lines and the problem is not there anymore.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-506


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-506
    Summary: Non-deterministic? failure of generated proxies
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
   Fix Fors:
             2.1 rc1
   Versions:
             2.0.3

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Fri, 28 Nov 2003 3:59 AM
    Updated: Fri, 28 Nov 2003 6:40 AM
Environment: redhat linux 9, j2se 1.4.2 (build 1.4.2-b28), postgres, hibernate 2.0.3

Description:
Suppose we have a class hierarchy A <- B, A <- C. Both class B and C have a method getX(). Suppose, moreover, that we have a class R that contains a reference to A.

If we do a query on class R and then a query on class B or C, we *sometimes* get a ClassCastException for the generated proxy when we try to call getX(). In my environment, the same test case succeeds or fails upon repeated execution.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-506) Non-deterministic? failure of generated proxies

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Fri, 28 Nov 2003 6:38 AM
       Body:
hmm...I see similar behavior when running this from inside eclipse.

When run as debug: classcastexception
When run as app: works fine...

Gotta be some weird classloader shit....i'm looking into it
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-506


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-506
    Summary: Non-deterministic? failure of generated proxies
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Fri, 28 Nov 2003 3:59 AM
    Updated: Fri, 28 Nov 2003 6:38 AM
Environment: redhat linux 9, j2se 1.4.2 (build 1.4.2-b28), postgres, hibernate 2.0.3

Description:
Suppose we have a class hierarchy A <- B, A <- C. Both class B and C have a method getX(). Suppose, moreover, that we have a class R that contains a reference to A.

If we do a query on class R and then a query on class B or C, we *sometimes* get a ClassCastException for the generated proxy when we try to call getX(). In my environment, the same test case succeeds or fails upon repeated execution.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-506) Non-deterministic? failure of generated proxies

[<leg...@at...>]

The following issue has been updated:

    Updater: Panagiotis Louridas (mailto:plo...@ya...)
       Date: Fri, 28 Nov 2003 4:01 AM
    Comment:
I attach a simple test case illustrating the issue. When run with junit, the same test may succeed or fail on repeated invocations.
    Changes:
             Attachment changed to hibernate_report3.tar.gz
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-506&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-506


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-506
    Summary: Non-deterministic? failure of generated proxies
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Fri, 28 Nov 2003 3:59 AM
    Updated: Fri, 28 Nov 2003 4:01 AM
Environment: redhat linux 9, j2se 1.4.2 (build 1.4.2-b28), postgres, hibernate 2.0.3

Description:
Suppose we have a class hierarchy A <- B, A <- C. Both class B and C have a method getX(). Suppose, moreover, that we have a class R that contains a reference to A.

If we do a query on class R and then a query on class B or C, we *sometimes* get a ClassCastException for the generated proxy when we try to call getX(). In my environment, the same test case succeeds or fails upon repeated execution.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-506) Non-deterministic? failure of generated proxies

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-506


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-506
    Summary: Non-deterministic? failure of generated proxies
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Fri, 28 Nov 2003 3:59 AM
    Updated: Fri, 28 Nov 2003 3:59 AM
Environment: redhat linux 9, j2se 1.4.2 (build 1.4.2-b28), postgres, hibernate 2.0.3

Description:
Suppose we have a class hierarchy A <- B, A <- C. Both class B and C have a method getX(). Suppose, moreover, that we have a class R that contains a reference to A.

If we do a query on class R and then a query on class B or C, we *sometimes* get a ClassCastException for the generated proxy when we try to call getX(). In my environment, the same test case succeeds or fails upon repeated execution.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-500) Improve reflection optimizer error message

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Max Rydahl Andersen
       Date: Thu, 27 Nov 2003 9:38 PM

yup - it's done
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-500


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-500
    Summary: Improve reflection optimizer error message
       Type: Patch

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 rc1
   Versions:
             2.1

   Assignee: Max Rydahl Andersen
   Reporter: Chris Nokleberg

    Created: Tue, 25 Nov 2003 3:10 PM
    Updated: Thu, 27 Nov 2003 9:38 PM

Description:
This patch changes the "reflection optimizer disabled" error message to (when possible) indicate the property which caused the failure.


---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Reopened: (HB-363) Constraint.java does not support CascadeConstraintsString

[<leg...@at...>]

Message:

   The following issue has been reopened.

   Reopener: Max Rydahl Andersen
       Date: Thu, 27 Nov 2003 9:37 PM

to fast on my fingers ;)
will fix later
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-363


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-363
    Summary: Constraint.java does not support CascadeConstraintsString
       Type: Bug

     Status: Reopened
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 rc1
   Versions:
             2.1 beta 3

   Assignee: Max Rydahl Andersen
   Reporter: ron lussier

    Created: Thu, 25 Sep 2003 1:38 PM
    Updated: Thu, 27 Nov 2003 9:37 PM
Environment: Mac OS X, Frontbase

Description:
In order to properly support SQL92, a change is required to allow the 'alter table ... drop constraint' statement to take a drop behavior.  This change affects net.sf.hibernate.mapping.Constraint.java, line 43.  I would like the line to read:

   return "alter table " + getTable().getQualifiedName(dialect) +
          " drop constraint " + getName() +
          dialect.getCascadeConstraintsString();

Frontbase (the dialect I contributed) requires either 'CASCADE' or 'RESTRICT' in a drop constraint clause.  (Frontbase is VERY SQL/92 standard, sometimes annoyingly.)  Isn't this what the dialect.getCascadeConstraintsString() property is for?  (The documentation for the property reads 'Completely optional cascading drop clause'.)

According to the documentation for SQL/92 (from http://www.contrib.andrew.cmu.edu/~shadow/sql/sql2bnf.aug92.txt), the syntax should be:

   <alter table statement> ::=
       ALTER TABLE <table name> <alter table action>

   <alter table action> ::=
         <add column definition>
       | <alter column definition>
       | <drop column definition>
       | <add table constraint definition>
       | <drop table constraint definition>

   <drop table constraint definition> ::=
       DROP CONSTRAINT <constraint name> <drop behavior>

   <drop behavior> ::= CASCADE | RESTRICT

The requirement of CASCADE or RESTRICT is also affirmed in "A Guide to the SQL Standard", Fourth Edition, on page 106, where the syntax is given as:

   base-table-alteration
      ::= ALTER TABLE base-table base-table-alteration-action

   base-table-alteration-action
      ::=   column-alteration-action
            | base-table-constraint-alteration-action

   base-table-constraint-alteration-action
      ::=    ADD base-table-constraint-definition
            | DROP CONSTRAINT constraint { RESTRICT | CASCADE }

On page 38 of the same volume, under 'Notation', the book states "Braces '{' and '}' are used to indicate that the material enclosed in those braces consists of a set of two or more items (separated by vertical bars) from which exactly one is to be chosen.

If you would prefer, I would be fine with creating a new, optional property of Dialect.java for this purpose, but I think that Hibernate needs something.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-363) Constraint.java does not support CascadeConstraintsString

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Max Rydahl Andersen
       Date: Thu, 27 Nov 2003 9:25 PM

done in CVS - please test ;)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-363


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-363
    Summary: Constraint.java does not support CascadeConstraintsString
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 rc1
   Versions:
             2.1 beta 3

   Assignee: Max Rydahl Andersen
   Reporter: ron lussier

    Created: Thu, 25 Sep 2003 1:38 PM
    Updated: Thu, 27 Nov 2003 9:25 PM
Environment: Mac OS X, Frontbase

Description:
In order to properly support SQL92, a change is required to allow the 'alter table ... drop constraint' statement to take a drop behavior.  This change affects net.sf.hibernate.mapping.Constraint.java, line 43.  I would like the line to read:

   return "alter table " + getTable().getQualifiedName(dialect) +
          " drop constraint " + getName() +
          dialect.getCascadeConstraintsString();

Frontbase (the dialect I contributed) requires either 'CASCADE' or 'RESTRICT' in a drop constraint clause.  (Frontbase is VERY SQL/92 standard, sometimes annoyingly.)  Isn't this what the dialect.getCascadeConstraintsString() property is for?  (The documentation for the property reads 'Completely optional cascading drop clause'.)

According to the documentation for SQL/92 (from http://www.contrib.andrew.cmu.edu/~shadow/sql/sql2bnf.aug92.txt), the syntax should be:

   <alter table statement> ::=
       ALTER TABLE <table name> <alter table action>

   <alter table action> ::=
         <add column definition>
       | <alter column definition>
       | <drop column definition>
       | <add table constraint definition>
       | <drop table constraint definition>

   <drop table constraint definition> ::=
       DROP CONSTRAINT <constraint name> <drop behavior>

   <drop behavior> ::= CASCADE | RESTRICT

The requirement of CASCADE or RESTRICT is also affirmed in "A Guide to the SQL Standard", Fourth Edition, on page 106, where the syntax is given as:

   base-table-alteration
      ::= ALTER TABLE base-table base-table-alteration-action

   base-table-alteration-action
      ::=   column-alteration-action
            | base-table-constraint-alteration-action

   base-table-constraint-alteration-action
      ::=    ADD base-table-constraint-definition
            | DROP CONSTRAINT constraint { RESTRICT | CASCADE }

On page 38 of the same volume, under 'Notation', the book states "Braces '{' and '}' are used to indicate that the material enclosed in those braces consists of a set of two or more items (separated by vertical bars) from which exactly one is to be chosen.

If you would prefer, I would be fine with creating a new, optional property of Dialect.java for this purpose, but I think that Hibernate needs something.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-345) <schemaexport> task "output" attribute doesn't respect relative build.xml directory path

[<leg...@at...>]

Message:

   The following issue has been re-assigned.

   Assignee: Christian Bauer (mailto:chr...@hi...)
   Assigner: Gavin King (mailto:ga...@hi...)
       Date: Thu, 27 Nov 2003 9:23 PM
    Comment:
Christian, would you see if this needs fixing? TIA
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-345


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-345
    Summary: <schemaexport> task "output" attribute doesn't respect relative build.xml directory path
       Type: Bug

     Status: Open
   Priority: Minor

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.1 beta 4

   Assignee: Christian Bauer
   Reporter: Keith Donald

    Created: Thu, 18 Sep 2003 10:57 AM
    Updated: Thu, 27 Nov 2003 9:23 PM
Environment: Windows XP + Eclipse was the environment in which this problem was noticed.

Description:
The following is an example use of the schema export task in ANT illustrating the problem:

    	<schemaexport properties="${conf.home}/hibernate.properties"
    	                   quiet="no" text="no" drop="no"
	                   delimiter=";"
	                   output="dist/conf/schema-export.sql">
        	<fileset dir="${build.home}/classes">
            	<include name="**/*.hbm.xml"/>
	        </fileset>
    	</schemaexport>

The directory "dist/conf/schema-export" is a relative path from the directory in which the ant build.xml file is located.  I get a "Schema test failed: path not found dist/conf/schema-export.sql" - it appears output is an absolute path and not a relative one.  This seems to only cause problems in Eclipse, but manually specifiying the working directory in which the build.xml file should execute doesn't solve the problem either.  It's also strange how ${conf.home} above in the properties attribute is also a relative path and it works great--the problem seems localized to the output attribute

Workaround: putting a ${basedir}/ in front of "dist/conf/schema-export.sql" above solves the problem.


---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-478) Foreign Key constraints duplicated with SchemaUpdate

[<leg...@at...>]

Message:

   The following issue has been re-assigned.

   Assignee: Christian Bauer (mailto:chr...@hi...)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-478


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-478
    Summary: Foreign Key constraints duplicated with SchemaUpdate
       Type: Bug

     Status: Open
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: Christian Bauer
   Reporter: Gerjon de Vries

    Created: Tue, 18 Nov 2003 10:48 AM
    Updated: Thu, 27 Nov 2003 9:21 PM
Environment: MySql 4.0.16-Max, mysql-connector-java-3.0.9-stable-bin, InnoDB tables, Linux (SuSe 9.0).

Description:
When using SchemaUpdate to create/alter table definitions, each consecutive use of "SchemaUpdate(configuration).execute(true)" will regenerate all foreign key constraint commands (e.g. "ALTER TABLE X add index(fromId), add constraint FK2065BD77CB5B07 foreign key (fromId) references Y(id)"). Effectively you get duplicates for each key, which might degrade performance, and after some time cause errors, since MySql allows a limited number of FK's.

It seems to me that this is caused by a mismatch of the constraint names in net.sf.hibernate.mapping.Table and net.sf.tool.hbm2ddl.TableMetaData, but I'm not 100% sure. The "ALTER TABLE ..." is generated in Configuration.java:462.

Note that I'm using InnoDB tables (for the transaction support). Also note that the problem will only reproduce with mysql-connector-java-3.0.8-stable-bin (or newer), since older versions have a bug with requesting foreign key information on InnoDB tables.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-409) SchemaUpdate fails on MySQL 4.0.11 because table name case sensitivity

[<leg...@at...>]

Message:

   The following issue has been re-assigned.

   Assignee: Christian Bauer (mailto:chr...@hi...)
   Assigner: Gavin King (mailto:ga...@hi...)
       Date: Thu, 27 Nov 2003 9:21 PM
    Comment:
Christian, you now own SchemaUpdate ;)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-409


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-409
    Summary: SchemaUpdate fails on MySQL 4.0.11 because table name case sensitivity
       Type: Bug

     Status: Open
   Priority: Major

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.0.3

   Assignee: Christian Bauer
   Reporter: Toni Bennasar Obrador

    Created: Sat, 18 Oct 2003 5:44 PM
    Updated: Thu, 27 Nov 2003 9:21 PM
Environment: Mandrake Linux 9.1 on x86, using MySQL 4.0.11 and official MySQL JDBC v3.0.9 , and Hibernate 2.0.3

Description:
Hello. I have the following problems:
I try to do a SchemaUpdate over a MySQL DB over database where the update should add some fields to some table, but the SchemaUpdate try to re-create the table, with <<SQLException>> results...

I did a debug to see what happens and the problem is at net.sf.hibernate.tool.hbm2ddl.DatabaseMetadata at line 47 , where the tool finds if the table exists or not, to create or update the table, :

public TableMetadata getTableMetadata(String name) throws HibernateException {

...

String[] types = {"TABLE"};
ResultSet rs = null;
try {
   try {

THIS>>rs = meta.getTables(null, "%", name.toUpperCase(), types);
      while ( rs.next() ) {
      if ( name.equalsIgnoreCase( rs.getString("TABLE_NAME") ) ) {
         table = new TableMetadata(rs, meta);
         tables.put( name.toUpperCase(), table );
         break;
      }

The line 47 is rs=meta.getTables(null, "%", name.toUpperCase(),Types);
The problem is that hibernate creates the tables (with SchemaExport) with lower case, and MySQL is case sensitive for table names on Unix (see http://www.mysql.com/doc/en/Name_case_sensitivity.html). But the .getTables call finds the upper case table name. Then, never is found, and it try to create the table when it exists.

The fix is remove the .toUpperCase() :
rs = meta.getTables(null, "%", name, types);

or SchemaExport should create the tables with upper case.

Hibernate is great. Thanks for all.





---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-498) extra info to add to LazyInitializationException

[<leg...@at...>]

Message:

   The following issue has been re-assigned.

   Assignee: Gavin King (mailto:ga...@hi...)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-498


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-498
    Summary: extra info to add to LazyInitializationException
       Type: Improvement

     Status: Open
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: Gavin King
   Reporter: francisco hernandez

    Created: Tue, 25 Nov 2003 8:12 AM
    Updated: Thu, 27 Nov 2003 9:20 PM

Description:
whenever a LazyInitializationException is thrown can you put in the message what object and method was called that threw the exception? 

this would be extremely helpfull.


---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-363) Constraint.java does not support CascadeConstraintsString

[<leg...@at...>]

Message:

   The following issue has been re-assigned.

   Assignee: Max Rydahl Andersen (mailto:xa...@xa...)
   Assigner: Gavin King (mailto:ga...@hi...)
       Date: Thu, 27 Nov 2003 9:18 PM
    Comment:
Max?
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-363


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-363
    Summary: Constraint.java does not support CascadeConstraintsString
       Type: Bug

     Status: Open
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 3

   Assignee: Max Rydahl Andersen
   Reporter: ron lussier

    Created: Thu, 25 Sep 2003 1:38 PM
    Updated: Thu, 27 Nov 2003 9:18 PM
Environment: Mac OS X, Frontbase

Description:
In order to properly support SQL92, a change is required to allow the 'alter table ... drop constraint' statement to take a drop behavior.  This change affects net.sf.hibernate.mapping.Constraint.java, line 43.  I would like the line to read:

   return "alter table " + getTable().getQualifiedName(dialect) +
          " drop constraint " + getName() +
          dialect.getCascadeConstraintsString();

Frontbase (the dialect I contributed) requires either 'CASCADE' or 'RESTRICT' in a drop constraint clause.  (Frontbase is VERY SQL/92 standard, sometimes annoyingly.)  Isn't this what the dialect.getCascadeConstraintsString() property is for?  (The documentation for the property reads 'Completely optional cascading drop clause'.)

According to the documentation for SQL/92 (from http://www.contrib.andrew.cmu.edu/~shadow/sql/sql2bnf.aug92.txt), the syntax should be:

   <alter table statement> ::=
       ALTER TABLE <table name> <alter table action>

   <alter table action> ::=
         <add column definition>
       | <alter column definition>
       | <drop column definition>
       | <add table constraint definition>
       | <drop table constraint definition>

   <drop table constraint definition> ::=
       DROP CONSTRAINT <constraint name> <drop behavior>

   <drop behavior> ::= CASCADE | RESTRICT

The requirement of CASCADE or RESTRICT is also affirmed in "A Guide to the SQL Standard", Fourth Edition, on page 106, where the syntax is given as:

   base-table-alteration
      ::= ALTER TABLE base-table base-table-alteration-action

   base-table-alteration-action
      ::=   column-alteration-action
            | base-table-constraint-alteration-action

   base-table-constraint-alteration-action
      ::=    ADD base-table-constraint-definition
            | DROP CONSTRAINT constraint { RESTRICT | CASCADE }

On page 38 of the same volume, under 'Notation', the book states "Braces '{' and '}' are used to indicate that the material enclosed in those braces consists of a set of two or more items (separated by vertical bars) from which exactly one is to be chosen.

If you would prefer, I would be fine with creating a new, optional property of Dialect.java for this purpose, but I think that Hibernate needs something.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-500) Improve reflection optimizer error message

[<leg...@at...>]

Message:

   The following issue has been re-assigned.

   Assignee: Max Rydahl Andersen (mailto:xa...@xa...)
   Assigner: Gavin King (mailto:ga...@hi...)
       Date: Thu, 27 Nov 2003 9:18 PM
    Comment:
You wanna apply this patch?
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-500


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-500
    Summary: Improve reflection optimizer error message
       Type: Patch

     Status: Open
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1

   Assignee: Max Rydahl Andersen
   Reporter: Chris Nokleberg

    Created: Tue, 25 Nov 2003 3:10 PM
    Updated: Thu, 27 Nov 2003 9:18 PM

Description:
This patch changes the "reflection optimizer disabled" error message to (when possible) indicate the property which caused the failure.


---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira