I can see a flame war coming up on this topic. Personally I would imagine that the database with proper indexes should perform adequately using a single table for this. I seriously doubt that there is a signifant performance improvement by splitting the data into multiple tables. I would suggest you use a single Entity with a single table and add and index on the location column.
Just my 2 cents worths. If you actually have done some analysis on this using both models I would be very interested in the statistics.If it's just a hunch I would use one table and spend the money saved in development time on faster drives. :-) Alex View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921052#3921052 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921052 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
