Open p-wieland opened 4 years ago
+1 stumbled upon this issue too and basically had to remove usage of __abstract_node__
I think I stumbled upon this too, I did some light digging, and it seems that neomodel does not create labels for classes marked abstract. This then breaks some things.
Maybe it's possible to add an override to "force" add a label, even for abstract nodes? It might also be possible to automatically detect if there are edges targeting this abstract node type and include the label only then?
Hi,
if I take the example regarding relationships and inheritance from the docs
and add
__abstract_node__ = True
to the base classBasePerson
and run the next code blockI get an error
I'm using neomodel 4.0.1
googling revealed that there have been issues with abstract nodes (#234 , #262 )