Re: trying out caching

> However, the following exception is common to the range of cache > implementations I've tried. I'm using datanucleus-core.4.1.7.jar > I'll see if Andy will talk to me .. > - java.lang.ClassCastException > - org.datanucleus.identity.SCOID cannot be cast to java.io.Serializable > - >

Re: trying out caching

> Caused by: org.datanucleus.exceptions.NucleusException: Error creating > cache >at > org.datanucleus.cache.JavaxCacheLevel2Cache.( > JavaxCacheLevel2Cache.java:98) You did not put a Javax.cache provider in your CLASSPATH. As Oscar suggested. DataNucleus provides "a simple wrapper to

Re: Why data nucleus over hibernate ?

> Why does Apache ISIS use DataNucleus over Hibernate, despite hibernate being > faster than datanucleus While it is very much for Apache ISIS team members to decide what they use (or provide access to) and why, and I'm not part of that process, I will reply however due to the "statement" made

Re: Binary, non-base 64 upload

> With respect to the storage of the BLOBs themselves, I don't think (at > least I couldn't find) any datatype mapping to be able to map from a stream > (obtained from ServletInputStream) into a JDO entity, ie to avoid the > creation of the BLOB in-memory. If it *were* possible, then I don't

Re: Redefining schema name in config file (to override JDO class annotation setting)

> What I've found is that by adding a file SimpleObject.jdo (in the > domainapp/dom/simple package, right alongside SimpleObject.java), with the > contents: > > > http://xmlns.jcp.org/xml/ns/jdo/jdo; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; >

Re: How to set up Apache Isis with neo4j 3.x with from scratch

1. You have added datanucleus-neo4j v5 to an existing Apache ISIS config (which uses datanucleus-core, datanucleus-api-jdo v4.1), but datanucleus-neo4j v5 REQUIRES datanucleus-core v5 datanucleus-api-jdo v5 Consequently you get NoSuchMethodError for a method that was ADDED in v5 (called from

Re: Emulating left outer joins with JDOQL

On Friday 22 Jan 2016 19:25:24 Andy Jefferson wrote: > > > SELECT p.*, t.* FROM Person p > > > LEFT JOIN PersonTemplate pt ON p.id = pt.personId > > > LEFT JOIN Template t ON pt.templateId = t.id > > > > > > With this query, I can get Persons even if

Re: Emulating left outer joins with JDOQL

> The query I'd like to perform is something like: > > SELECT p.*, t.* FROM Person p > LEFT JOIN PersonTemplate pt ON p.id = pt.personId > LEFT JOIN Template t ON pt.templateId = t.id > > With this query, I can get Persons even if they don't have a Template. Which is what you would do if you

Re: Emulating left outer joins with JDOQL

> > SELECT p.*, t.* FROM Person p > > LEFT JOIN PersonTemplate pt ON p.id = pt.personId > > LEFT JOIN Template t ON pt.templateId = t.id > > > > With this query, I can get Persons even if they don't have a Template. > Which is what you would do if you followed the example I suggested, using >

Re: Emulating left outer joins with JDOQL

> Person > - String name > > Template > - String name > - String field1 > - boolean otherBunchOfProperties > > PersonTemplate > - Person person > - Template template > I want to query all Persons along with their corresponding Template > through PersonTemplate. > Adding the Template property

Re: datanucleus foreign key name

>> Just interested to know if there is any way to stop DataNucleus adding _oid >> to the end of all its generated foreign keys, this it with >> @PersistenceCapable( identityType = IdentityType.DATASTORE)? >> It adds _id_oid to the tail of them all so wondering why? > > Don't know why it does it