I wonder that if I can handle the below scenario via Hibernate,
if yes that would be perfect.

In standard class mapping, we set the table where that class instances will be saved to. But I have some strange need,
I dont want to give a table name in the beginning of the class mapping,
in runtime according to user selection, the table that the instances will be changed, a small example:

Class Cars {
Long id;
String type;
String model;
....

}

In gui, user create a new car and set its type say; car.setType("sport");

and then called save, what I want, is saving this data to the table "@type@Car", may exist or not (hibernate creates non-existing tables)
in that example, the generated table will be "sportCAR" and that data will be saved to that table. Since I do not know all car types, I cant map them by table per concrete class mapping strategy in the initialization of hibernate and the configuration files.

Can I do such implementaion via hibernate?

can such a class mapping be done

class name ="CAR" table = @propert1ValueCAR@
...
...
<property name = "property1" Column = "Property1" ...

no - hibernate cant do that.


but you could probably easily implement on top of hibernate - just generate a mapping that states what you need and rebuild your Configuration/SessionFactory.

Hi Borak,

Why do you want to use different tables for different values of your 'type' property? That is certainly novel, I imagine you must have some good reason for wanting to do that, but I don't suppose I know what the reason is, and I am curious...

—ml—

One reason might be:

Class Userdata
{
long id;
String name;
Some Data Properties...
}

If each user has millions of rows (gigas of data) of UserData, it might be better to persist UserData to different tables. Each user has its own table Userdata@id. This may improve performance, I think.