You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2018. It is now read-only.
Hey there!
I am sorry that I can not offer a pull request, I just don't understand data mapper well enough.
With the SQLite adapter, Booleans are transformed to 't' and 'f' in the queries. These string values are typecasted to false by sqlite. So datamapper persists the wrong values.
Please help me fix that.
The text was updated successfully, but these errors were encountered:
I have no idea what adapter you're using for Sqlite... but, searching around I found this repository, which is actually an FFI (foreign language interface) with both C and Java code behind it.
It seems the code in question might be here... there are single quotes inside the double quotes and that might (or might not) be the issue... but I'm just passing by and I know nothing about any of this.
I hope this helps and that I did;t make a mess of things. If the issue is something specific on your machine or in your code (like you manually using 't' and 'f' instead of true and false) than I hope this will get things rolling.
@FeeJai I'd need more information about which gems you're using, and on which version of Ruby. I can't seem to reproduce this behavior. Can you provide more information about what you're doing?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey there!
I am sorry that I can not offer a pull request, I just don't understand data mapper well enough.
With the SQLite adapter, Booleans are transformed to 't' and 'f' in the queries. These string values are typecasted to false by sqlite. So datamapper persists the wrong values.
Please help me fix that.
The text was updated successfully, but these errors were encountered: