Having a big table to mapping, I’m thinking to divide it into more different
physical table in order to be able to tune better the used cache. What do you
think about it ? Is there any other possibility to find out the problem without
divide the database table ? I’m thinking to database table portioning and/or
Hibernate query result caching.
For instance We may have the following scenario:
a table containing all the bus stop around the world for each bus
provider
a Web Services to book a bus trip
If we have just one bus provider mostly used how we can cache just
its bus station ?
Thank in advance and best regards Renato.
If you are not the intended recipient of this e-mail message, please notify the
sender
and delete all copies immediately. The sender believes this message and any
attachments
were sent free of any virus, worm, Trojan horse, and other forms of malicious
code.
This message and its attachments could have been infected during transmission.
The
recipient opens any attachments at the recipient's own risk, and in so doing,
the
recipient accepts full responsibility for such actions and agrees to take
protective
and remedial action relating to any malicious code. Travelport is not liable
for any
loss or damage arising from this message or its attachments.
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
