-
Notifications
You must be signed in to change notification settings - Fork 27
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
Incomplete support for SQLAlchemy types #23
Comments
SQLa Numeric types get returned as decimal.Decimal objects. simplejson has support for this, whereas the builtin json module does not and there's no clean way to subclass it in a way that it won't convert the value to a JSON string. Fixes ColtonProvias#23
SQLa Numeric types get returned as decimal.Decimal objects. simplejson has support for this, whereas the builtin json module does not and there's no clean way to subclass it in a way that it won't convert the value to a JSON string. Fixes ColtonProvias#23
SQLa Numeric types get returned as decimal.Decimal objects. simplejson has support for this, whereas the builtin json module does not and there's no clean way to subclass it in a way that it won't convert the value to a JSON string. Fixes ColtonProvias#23
So I have a fix, but I had to go back a dozen commits or so to find a commit that wasn't broken to branch from. Any chance you can put the unfinished stuff into a separate branch and get master back in a clean state so I can submit a proper PR and get this fix released? |
I just branched the 4.x.x branch off so you can submit the fix to there. |
Thanks, I'll update my branch and get a PR up later tonight. |
SQLa Numeric types get returned as decimal.Decimal objects. simplejson has support for this, whereas the builtin json module does not and there's no clean way to subclass it in a way that it won't convert the value to a JSON string. Fixes ColtonProvias#23
Ok, it ended up being a few days before I could get to it, but PR is up now. |
I have a similar issue with Data type. any advice on how to handle that, please? |
Running into this error with a postgres numeric type which leverages
decimal.Decimal
under the hood:I think I see how to add it, so I'll put up a PR if I'm successful.
The text was updated successfully, but these errors were encountered: