I am not meaning one pojo with its fields in different tables.

I mean one pojo with multiple tables which own the same structure.

Since I am fraid the table may change too large,so I wonder if there is any way?

I have read the docs of hibernate shard,however I found it is rather complex...

Hi,
It is possible to have tables with identical structure, but they would have to have different names. However splitting records for the same POJO entity across two different tables is not a good idea! Why do you want to do this?

Kate

YEs, it is not a good idea.

We are doing a log(tomcat) analyzer,so we first push all the log to the table per day.

So the records in the table will grow speedly!

That's why we look for a way to slove this problem.

Hi,

You cannot create more than one identical table so that would not work. Storing raw logs in a database probablty isnt the best solution, it would be better to store structured data after processing the logs which would work well in a database.

Hope that helps,

Kate

This is the structure of the table:


The log pushed to table is filtered yet,some raw request(http:/.../xx.gif is excluded).

Even so,the records will grow also. One year two years later?

Hi,

Having large numbers of records in a table is not necessarily problem, they can frequently run into millions of records without encountering performance issues. However, if you have concerns you might want to consider partitioning. How you do this will depend highly on what database you are using, and you would need configure this separately. Hibernate has no inherent support for partitioning but it is possible to manipulate Hibernate so that it can access partioned tables. A quick search has thrown up this article: http://blog.xebia.com/2006/07/31/partitioning-in-hibernate/ which you may want to take a look at.

Hope that gives you some guidance,
Kate.

Thanks for your kind.:)

In fact ,I have thought of partitioning in mysql,and I think it is not related to the oRM framework. But even thougth,we are afriad of put all the data in one table. :(

Form your answer,and that article,I decide not map one entity to multiple tables. I will use the partitioning in mysql when needed.

Thank you very much. :)