-
Notifications
You must be signed in to change notification settings - Fork 227
Support for Custom Column Types? #53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Ah, I can register them the same way the converters are registered in converter.py Sorry for the bother! |
Can you explain how you did this? Did you just modify the source, or was there a better way of adding another type? |
I just ran into this same issue as well. We have several custom subclasses of Currently the solution is to modify Importing out custom types decorating the I'd love to know of a better solution without modifying graphene_sqlalchemy. |
You don't have to use the
Whenever your schema is imported and run, the conversion will also be registered. |
Awesome thanks for the tip. This allowed me to move the decorators and leave the module unmodified. Thanks! |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related topics referencing this issue. |
I don't see anything in the documentation and a brief look through the source code didn't reveal anything immediately. I have a custom GUID type (as documented in the sqlalchemy docs here: http://docs.sqlalchemy.org/en/latest/core/custom_types.html#backend-agnostic-guid-type) and when I try to use the SQLAlchemyObjectType with the model metaclass, it doesn't know how to convert type GUID. Is there a way to handle these custom column types? Do I need to just subclass SQLAlchemyObjectType and make it understand what that is?
Thanks for any help.
The text was updated successfully, but these errors were encountered: