Console server initialization fails with Oracle 11g

[lucasmcgrew]

The problem is the table named 'user' which is a reserved word in oracle, so the table cannot be created:

10148 [main] ERROR org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: create table user (id number(19,0) not null, version number(19,0) not null, username varchar2(255 char) not null unique, primary key (id))
10148 [main] ERROR org.hibernate.tool.hbm2ddl.SchemaUpdate - ORA-00903: invalid table name

I assume the same issue will be present with Postgres database servers and perhaps others. Hibernate 3.5+ appears to have a potential solution, but I'm not too familiar with grails/hibernate version compatibility:

http://docs.jboss.org/hibernate/core/3.5/api/org/hibernate/cfg/Environment.html#GLOBALLY_QUOTED_IDENTIFIERS

[ypujante]

I believe there is a way to 'map' a domain object to a different table
name. I do not know if this can be externalized. It is not trivial to
change it now for backward compatibility reasons. It would clearly be
better if that was an option. If anybody has any idea on how to do it in
grails, please let me know.

Thanks
Yan

On Thu, Dec 8, 2011 at 1:30 PM, lucasmcgrew <
reply@reply.github.com

wrote:

The problem is the table named 'user' which is a reserved word in oracle,
so the table cannot be created:

10148 [main] ERROR org.hibernate.tool.hbm2ddl.SchemaUpdate -
Unsuccessful: create table user (id number(19,0) not null, version
number(19,0) not null, username varchar2(255 char) not null unique, primary
key (id))
10148 [main] ERROR org.hibernate.tool.hbm2ddl.SchemaUpdate - ORA-00903:
invalid table name

I assume the same issue will be present with Postgres database servers and
perhaps others. Hibernate 3.5+ appears to have a potential solution, but
I'm not too familiar with grails/hibernate version compatibility:

http://docs.jboss.org/hibernate/core/3.5/api/org/hibernate/cfg/Environment.html#GLOBALLY_QUOTED_IDENTIFIERS

---

Reply to this email directly or view it on GitHub:
https://github.com/linkedin/glu/issues/111

[ypujante]

Thanks to Chris, I was able to allow renaming the table via a configuration parameter. This will make it in the next release (http://glu.977617.n3.nabble.com/console-with-PostgreSQL-td4024802.html)

[ypujante]

Fixed with 4.4.2