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

Coercing values during chaining

uranusjr opened this issue Dec 17, 2013 · 1 comment

Coercing values during chaining #33

uranusjr opened this issue Dec 17, 2013 · 1 comment


Copy link

uranusjr commented Dec 17, 2013

This works

>>> print select('person', where={'id in': ('foo', 'bar')})
SELECT * FROM "person" WHERE "id" IN ('foo', 'bar')

But this doesn't

>>> print select('person', where={'id in': (1, 2, 3)})
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "mosql/", line 819, in __call__
    return self.stringify(*positional_values, **clause_args)
  File "mosql/", line 815, in stringify
    return self.format(clause_args)
  File "mosql/", line 801, in format
    return self.statement.format(clause_args)
  File "mosql/", line 752, in format
  File "mosql/", line 679, in format
    x = formatter(x)
  File "mosql/", line 359, in joiner_wrapper
    return f(x)
  File "mosql/", line 519, in build_where
    return _build_condition(x, identifier, value)
  File "mosql/", line 464, in _build_condition
    v = paren(concat_by_comma(v))
  File "mosql/", line 359, in joiner_wrapper
    return f(x)
  File "mosql/", line 383, in concat_by_comma
    return ', '.join(i)
TypeError: sequence item 0: expected string, int found

because join works only when the sequence contains str (and unicode) instances.

It seems pretty reasonable to coerce before concatenating values:

def concat_by_comma(i):
    '''A joiner function which concats the iterable by ``,`` (comma).'''
    return ', '.join(str(v) for v in i)

concat_by_space, concat_by_or and concat_by_and are all similar, I believe. Maybe extract the logic into a decorator?

There may be some encoding issues, too. I would rather use unicode instead of str, but you will need to add some version detection if so.

Copy link

moskytw commented Dec 17, 2013

It is a regression. I'm checking.

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

No branches or pull requests

2 participants