Properties should be inherited about gqlalchemy HOT 3 CLOSED

Oh, that's right. Because the database reference is removed from the property name once the User is created. It's an easy fix, when a subclass of Node is being created it can propagate the db object upwards. But then a user would have to define the Streamer as:

class Streamer(User, db):
    pass

The other option is what @jbajic and I talked earlier about, and that is creating a global instance of db that is going to be used everywhere. Very few users are going to use multiple databases, and we should cater the simplicity to the majority.

from gqlalchemy.

Oh, the functionality I mentioned is not implemented, it's a proposal.
But after giving it some thought, I think db arguments can be completely ignored when subclasses are created because the superclasses already created all constraints/indexes. I'll push a fix for this by the end of day.

from gqlalchemy.

Is it possible to add other properties to the Streamer then?
Because, when I try adding the db argument I get the following error:
TypeError: metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases

from gqlalchemy.