On 4/22/15 5:47 AM, Pavel S wrote:
If I turn warnings into errors, the problem is still the same:
1) where the error occured as the code path in traceback is not
pointing to the place where select() has been bound with values
that would suggest your code has some less typical form where you a
On 4/22/15 3:48 AM, Pavel S wrote:
Hi,
it happened to me many times during development, mainly when used
custom column types, that I passed wrong type of value to the query.
Then the the following warning was emitted:|
||
SAWarning: Unicodetype received non-unicode bindparam value
|
The pr
If I turn warnings into errors, the problem is still the same:
1) where the error occured as the code path in traceback is not pointing to
the place where select() has been bound with values
2) you don't know what was the value
Dne středa 22. dubna 2015 10:09:51 UTC+2 SElsner napsal(a):
>
> He
Hey,
you dan do:
import warnings
warnings.simplefilter('|error|')
This will raise an exception. and give you a stacktrace on where the
Unicode warnign happened.
On 04/22/2015 09:48 AM, Pavel S wrote:
Hi,
it happened to me many times during development, mainly when used
custom column t
Hi,
it happened to me many times during development, mainly when used custom
column types, that I passed wrong type of value to the query.
Then the the following warning was emitted:
SAWarning: Unicode type received non-unicode bindparam value
The problem with such warning is it does not say
1
