Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Hibernate database specific columnDefinition values

the problem is as follows: We're using hibernate with annotations as O/R Mapper.

Some @Column annotations look like:

@Column(columnDefinition = "longblob", name = "binaryData", nullable = true)

or

@Column(columnDefinition = "mediumtext", name = "remark", nullable = true)

with the columnDefinition attributes being mysql specific

on postgres for example, the columnDefinition values should be "bytea" and "varchar(999999)"

and on oracle probably something else.

Problems arise currently at the time of Schema Export, e.g. when creating the DDL statements.

Possible workarounds that I can think of are - Hack some JDBC driver that does a text replace (e.g. longblob->bytea) for the DDL statements. That's ugly but will work somehow - Use hibernate xml configuration instead of annotations. That will probably work but I prefer annotations

Does anybody know any alternatives? Hibernate specific workarounds are ok, e.g. if the columnDefinition attribute can contain dialect specific values like

@Column(columnDefinition = "mysql->mediumtext, postgres->varchar(999999)", name = "remark", nullable = true)

Thanks Holger

like image 687
user1946784 Avatar asked Dec 22 '09 07:12

user1946784


1 Answers

Why don't you use the database-agnostic annotations like:

  • @Lob (on a byte[] or a String property)
  • @Column(length=90000) (on a String property)

and see what columns will be generated in the database. They will most likely be of the types you want them to be.

like image 160
Bozho Avatar answered Sep 19 '22 15:09

Bozho