Hi guys,
About specific configurations, I'm wondering which strategy is the best:
- Putting all configuration into the general configuration files
(like persistence.xml or hibernate.properties)
- Having a specific for each ogm implementation (ispn-config.xml,
mongodb-config.xml)
And is there any
Hello,
For example, you you try to persist an object the method "public Tuple
getTuple(EntityKey key)" is called but you cannot try to look into the
database to check whether the persisted object already exists or not
because the EntityKey class doesn't provide any getter method about the
table o
OGM-40 will add those, it's next on my todo list. But you should not have do
read the DB to know if an object is already there. That's the job of the
hibernate engine and it is reflected in the dialect API. If you are missing
something, let me know.
On 3 mars 2012, at 11:32, Guillaume SCHEIBEL
It depends,
If your configuration is limited to 4 properties, then persistence.xml is best.
In Infinispan case,t he configuration of Infinispan is embedded and we have
decided to simply point to the file.
On the name space, today we do hibernate.ogm..
We might do hibernate.ogm.datastore.. later
Because Hibernate raises an exception if you call persist on an already
existing entry.
On 3 mars 2012, at 11:54, Guillaume SCHEIBEL wrote:
> Ok greate, so why the engine calls getTuple when I perform a persist if it's
> to check that the object to persist is already existing ?
>
> Guillaume
>
