generate « Oracle « JPA Q&A





1. Hibernate 2.0.3 generates incorrect SQL on oracle.    forum.hibernate.org

I've got a table on an Oracle 9i (9.2.0.1.0) with rather long column names, the longest of which is 29 characters. Oracle limits the name of a column to 30 characters. When I use Hibernate to fetch a record from the table, it generates the following statement: Code: select statetra0_.STATE_TRANSITION_CONDITION_ID as STATE_TR1___, operatio1_.OPERATION_NAME as OPERATION_NAME0_, operatio1_.OPERATION_CLASS as OPERATIO2_0_, statetra0_.STATE_TRANSITION_CONDITION_ID as STATE_TRANSITION_CONDITION_ID1_, ...

2. Oracle found syntax error in generated SQL    forum.hibernate.org

Author Message zdila Post subject: Oracle found syntax error in generated SQL Posted: Wed Jun 15, 2005 4:14 am Beginner Joined: Tue Apr 05, 2005 12:09 pm Posts: 48 Location: Slovakia (SK), Koice (KE) Hi hibernate gurus Please help me to solve this issue. Look at my mapping or suggest me a better one. I'll do one more post ...

3. Oracle 8i, Hibernate 3.1.3 problem with generated SQL    forum.hibernate.org

Newbie Joined: Fri Dec 12, 2003 2:12 am Posts: 16 I've been upgrading an application to Hibernate 3.1 (from 2.1) over the last few days, and I've come across a strange problem with an "Invalid column name" that Oracle 8i is passing back. The query runs fine in TOAD and as a PreparedStatement (copying what Hibernate is generating) using the same ...

4. Hibernate intermittantly generates invalid SQL (Oracle)    forum.hibernate.org

Occasionally, our automated unit tests will fail with an illegal SQL exception from Oracle, talking about SQL generated by Hiberate. It's never the same test, but always the same SQL. Has anyone else experienced this? I've attached the generated SQL below, note the difference in the from clause: select user0_.USER_ID as USER1_34_1_, user0_.USER_NAME as USER2_34_1_, user0_.STATUS as STATUS34_1_, user0_.CUSTOMER_ID as CUSTOMER4_34_1_, ...