[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-753?page=all ]
Max Rydahl Andersen updated HBX-753:
------------------------------------
Summary: Hibernate Tools should warn if user has generated ID class with Oracle LONG
data type (was: Hibernate Tools generates ID class with Oracle LONG data type)
Priority: Trivial (was: Minor)
downgrading priority + description.
Hibernate Tools should warn if user has generated ID class with
Oracle LONG data type
-------------------------------------------------------------------------------------
Key: HBX-753
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HBX-753
Project: Hibernate Tools
Type: Bug
Components: reverse-engineer
Environment: Hibernate 3.0, Oracle, Hibernate Tools 3.2 beta 7
Reporter: Dan Madoni
Priority: Trivial
If an Oracle table PK includes a LONG data type, Hibernate Tools dutifully generates an
ID class that includes that LONG field. Later on when you query with the generated mapped
classes, you get an "illegal use of LONG datatype" error (ORA-00997). This can
be particularly frustrating since the typical lazy developer (like me) happily goes off
and uses these generated classes, then is bewildered to run into an error in code he
didn't create or bother to look at since the nice tool did all the work. :)
The first thing you're going to say, "what kind of moron includes a LONG data
type as a PK anyway?" Suffice to say, such PK's exist and people like me have no
say in the matter. So considering that some of us are forced between a rock (some zany db
administrator) and a hard place (a requirement to use Hibernate), you can hopefully feel
our pain. :)
--
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