Hibernate replacing my tables

lkoskela · **Joined:** Mon Sep 27, 2004 3:01 am **Posts:** 17

Hi,

Why is Hibernate replacing existing tables in the database with its own, different tables upon a call to session.find("from X")?

Here's my mapping document:

Code:

    <class name="User" table="tdb_user">
        <id name="id" type="string" column="id">
            <generator class="uuid.hex"/>
        </id>
        <property name="username" column="username" type="string"/>
        <property name="realname" column="realname" type="string"/>
    </class>

Here's the class I'm mapping:

Code:

public class User {
    
    private String id;

    private String username;

    private String realname;

    public User() {
    }
    
    public String getId() {
        return id;
    }

    public void setId(String id) {
        this.id = id;
    }

    public String getUsername() {
        return username;
    }

    public void setUsername(String username) {
        this.username = username;
    }

    public String getRealname() {
        return realname;
    }

    public void setRealname(String name) {
        this.realname = name;
    }

}

And this is what I used for creating the table before triggering the SELECT from within Tomcat:

Code:

create table tdb_user (
  id VARCHAR(32) PRIMARY KEY,
  username VARCHAR(32) NOT NULL UNIQUE,
  password VARCHAR(32) DEFAULT NULL,
  realname VARCHAR(100) NOT NULL
) TYPE=InnoDB;

Note that I've included a 'password' column in the database and that isn't mapped to the User class.

Finally, this is what happens when Hibernate has had a chance to do the SELECT:

Code:

mysql> describe tdb_user;
+----------+--------------+------+-----+---------+-------+
| Field    | Type         | Null | Key | Default | Extra |
+----------+--------------+------+-----+---------+-------+
| id       | varchar(32)  |      | PRI |         |       |
| username | varchar(32)  |      | UNI |         |       |
| password | varchar(32)  | YES  |     | NULL    |       |
| realname | varchar(100) |      |     |         |       |
+----------+--------------+------+-----+---------+-------+
4 rows in set (0.00 sec)

mysql>
mysql> describe tdb_user;
+----------+--------------+------+-----+---------+-------+
| Field    | Type         | Null | Key | Default | Extra |
+----------+--------------+------+-----+---------+-------+
| id       | varchar(255) |      | PRI |         |       |
| username | varchar(255) | YES  |     | NULL    |       |
| realname | varchar(255) | YES  |     | NULL    |       |
+----------+--------------+------+-----+---------+-------+
3 rows in set (0.00 sec)

mysql>

I'd really appreciate any pointers towards where I'm going to the woods.

I'm using Hibernate 2.1.6 and MySQL 4.0.22.

-Lasse-

lkoskela · **Joined:** Mon Sep 27, 2004 3:01 am **Posts:** 17

Anyone?

anthony · **Posted:** Sat Nov 06, 2004 10:32 am

show hibernate.hbm.xml

lkoskela · **Joined:** Mon Sep 27, 2004 3:01 am **Posts:** 17

Thanks for looking into this.

Here's my hibernate.cfg.xml:

Code:

<!DOCTYPE hibernate-configuration PUBLIC 
   "-//Hibernate/Hibernate Configuration DTD//EN"
   "http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd">

<hibernate-configuration>
   <session-factory>
      <property name="show_sql">true</property>
      <mapping resource="com/domain/User.hbm.xml"/>
   </session-factory>
</hibernate-configuration>

And here's the User.hbm.xml:

Code:

<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC 
   "-//Hibernate/Hibernate Mapping DTD 2.0//EN"
   "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">
<hibernate-mapping>

    <class name="com.domain.User" table="tdb_user">
        <id name="id" type="string" column="id">
            <generator class="uuid.hex"/>
        </id>
        <discriminator column="usertype" type="string"/>
        <property name="username" column="username" type="string"/>
        <property name="realName" column="realname" type="string"/>
    </class>

</hibernate-mapping>

What I forgot to mention is that I'm using a user-provided connection, i.e. the Java code creates a Session as follows:

Code:

// this is called once per application
sessionFactory = new Configuration().configure().buildSessionFactory();

// this is called once per request
session = sessionFactory.openSession(connection);

max · **Posted:** Sat Nov 06, 2004 11:04 am

you probably have "hibernate.hbm2ddl.auto" set to something enabling automatic schemacreation... ?

lkoskela · **Joined:** Mon Sep 27, 2004 3:01 am **Posts:** 17

max wrote:

you probably have "hibernate.hbm2ddl.auto" set to something enabling automatic schemacreation... ?

Umm... No. Unless it's "true" by default. I'll try to explicitly set it to false and report back.

lkoskela · **Joined:** Mon Sep 27, 2004 3:01 am **Posts:** 17

Heck. It seemed to work. I added

Code:

which seemed to get rid of the problem (even though "off" is not a valid value for that property according to the docs...).

Is this the way it's supposed to work?

max · **Posted:** Sat Nov 06, 2004 11:26 am

check if you have a hibernate.properties file somewhere in your classpath (including inside .jars) that set this setting otherwise ?

lkoskela · **Joined:** Mon Sep 27, 2004 3:01 am **Posts:** 17

max wrote:

check if you have a hibernate.properties file somewhere in your classpath (including inside .jars) that set this setting otherwise ?

Ah. There it was. The default hibernate.properties file included this block:

Code:

## auto schema export

#hibernate.hbm2ddl.auto create-drop
hibernate.hbm2ddl.auto create
#hibernate.hbm2ddl.auto update

which obviously caused the behavior I saw, until I overrode it with .cfg.xml.

I definitely don't want create-drop and probably not create either (I like to fail fast...), but what does the "update" option do?

max · **Posted:** Sat Nov 06, 2004 12:30 pm

that setting is not so in the hibernate releases (maybe it was that once, but it was quickly fixed). ... are you using the latest release or have you modified that file by your own ?

lkoskela · **Joined:** Mon Sep 27, 2004 3:01 am **Posts:** 17

max wrote:

that setting is not so in the hibernate releases (maybe it was that once, but it was quickly fixed). ... are you using the latest release or have you modified that file by your own ?

I haven't modified it myself -- I just copied it from somewhere, probably the "adminapp" sample application sources.

max · **Posted:** Sat Nov 06, 2004 12:42 pm

lkoskela wrote:

max wrote:

that setting is not so in the hibernate releases (maybe it was that once, but it was quickly fixed). ... are you using the latest release or have you modified that file by your own ?

I haven't modified it myself -- I just copied it from somewhere, probably the "adminapp" sample application sources.

aah .... copy-pasted code/settings! Dangerous ;)

lkoskela · **Joined:** Mon Sep 27, 2004 3:01 am **Posts:** 17

max wrote:

aah .... copy-pasted code/settings! Dangerous ;)

You can say that again...