Skip to content
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

In table filter criterion editor, specifying empty strings (as well as NULLs) for the "between" values causes an error #465

Open
leehart opened this issue Jan 8, 2019 · 0 comments
Labels

Comments

@leehart
Copy link
Collaborator

leehart commented Jan 8, 2019

Home > Data > P.f.6.0 Release > Samples
Click "Add filter"
Click "Add criterion"
Select "Latitude" column
Select "Between" comparison
See that no values have been specified by default.
Click "Apply"
See error.

Note that if you (go back to the criterion editor and) click in the empty boxes and outside them (focus then blur), the empty strings are automatically converted to NULL values, which also causes an error.

(Maybe related to #463, i.e. monetdb type conversion.)
Except this is conversion of a particular string to a float:

OperationalError: 22018!conversion of string 'None' to type flt failed.

Instead of conversion of string to integer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants