[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5569) Hibernate should not use LONG type for Oracle

Hibernate should not use LONG type for Oracle --------------------------------------------- Key: HHH-5569 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5569 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0.Beta-1 Environment: 3.5.0.Beta-1, Oracle 9i Reporter: Mindaugas Žakšauskas This is a spin-off from http://stackoverflow.com/questions/3719905/why-has-hibernate-switched-to-.... With the changes introduced in HHH-3892 Hibernate started to use Oracle LONG type instead of CLOB for properties of type="text". This is a bad idea because of the following: * it creates huge amount of pain for people who depend on Hibernate automatically creating table structure for them. Tables created with the same mapping will have different structure than tables created with earlier version of Hibernate * Oracle LONG type has a limitation: there can be _only one_ column of this type within a single table; * Oracle has deprecated LONG type many years ago and advised against using this type ever since 8i. See http://www.orafaq.com/wiki/LONG. Defining a property to have type="clob" is not really a solution; other databases might have other, more suitable types to store this type of data (not necessarily CLOB). At the moment the only workaround is to define custom dialact and use it; but this is a very poor solution in the long term.