Yes, I think that if we keep the property and only add the label we
won't break anything in the mapping.
On Thu, Nov 17, 2016 at 2:15 PM, Guillaume Smet
wrote:
> Hi,
>
> As I understand it, having 2 labels means that you could search either with
> n:Person or n:Player?
>
> Thus if we keep the DT
Hi,
As I understand it, having 2 labels means that you could search either with
n:Person or n:Player?
Thus if we keep the DTYPE: Player in place in addition to both labels, we
won't break anything, will we?
--
Guillaume
On Thu, Nov 17, 2016 at 2:30 PM, Sanne Grinovero
wrote:
> Hi, it makes s
Hi, it makes sense but I don't think we can change the mapping now.
Could you do it as a new option? Would you be able to adjust the
queries as needed?
If you can make it a configuration property, default to the old style
mapping, and log a warning of using a deprecated mapping when the old
one i
A user created the issue https://hibernate.atlassian.net/browse/OGM-1210
The problem is that when we use the SingleTable strategy in Neo4j we
add a property DTYPE to the node to discriminate the entities instead
of using labels.
As an example, given an entity Player that extends Person we create
