No, the error is an UnicodeDecodeError (http://paste2.org/p/457059).
I can't just "try" a different DB, switch to SQLite, etc. As I've said, my
website is on production and I have a lot of users using it.
Also, the problem is something that started lately, probably because of some
content that a user has uploaded, so a new DB will work for sure, even if
it's the same kind. But, I need it to work with my DB, or a least understand
what caused it so I can make sure it never happens again.

I'll check my DBAPI, although I'm pretty sure it's that latest one that is
shipped with CentOS5.

Thank you,
Yo'av

2009/10/10 Michael Bayer <[email protected]>

>
> On Oct 10, 2009, at 3:43 AM, Yo'av Moshe wrote:
>
> Any ideas?
> I still don't understand why the query is failing even when I'm using a
> unicode object.
>
>
> whats the error ?  "EOF in multi-line statement" ?  thats not a SQLAlchemy
> error message.   what happens when you try SQLA 0.5.6 (perhaps there was
> some quirk regarding encoding that was fixed) ?  a different / latest
> version of your DBAPI (perhaps your DBAPI is misunderstanding a character as
> a newline ) ?  try SQLite with the same statement  ?  (what database are you
> using ?)
>
>
>
>
> Yo'av
>
> 2009/10/8 Yo'av Moshe <[email protected]>
>
>> Thanks, I didn't know about that awful IPython bug...
>>
>> I checked, and apparently my website is already doing the SA query with a
>> unicode object and not with a string one, so I think that it's not the u''
>> thing (it's true that I forgot it in my console testing, though).
>> What you showed about IPython explains why it didn't give me any result
>> when running in IPython with the unicode object - since it wasn't really a
>> unicode object.
>>
>> So again - I *am* querying SA with a unicode object, and still, it fails
>> the first time and works the second time.
>>
>> Yo'av.
>>
>> 2009/10/7 Wolodja Wentland <[email protected]>
>>
>>> On Wed, Oct 07, 2009 at 07:55 -0700, Yo'av Moshe wrote:
>>> > See what I mean here (it's me running the same query twice in
>>> > IPython): http://paste2.org/p/457059
>>> >
>>> > What can cause this behavior?! I can't think of anything! I guess that
>>> > one of my users has uploaded some article with some invalid utf8 code,
>>> > but should that kill the query? and how come it doesn't kill the
>>> > second one? and what can I do to avoid it?
>>>
>>> In addition to the bug Mike pointed out to you I want to introduce you
>>> to my favourite bug this year:
>>>
>>> https://bugs.launchpad.net/ipython/+bug/339642
>>>
>>> If you run into unicode issues with IPython it is wise to check the
>>> 'python' behaviour before development code against this bug.
>>>
>>> kind regards
>>>
>>>    Wolodja Wentland
>>>
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.10 (GNU/Linux)
>>>
>>> iQIcBAEBCAAGBQJKzMesAAoJEIt/fTDK8U78OTsP/jLC/OHMy7SqyM4T1OswUsfL
>>> 7V4JXjvxk7xSRUaUwWSqbi4FHYPUDVQ3iFD4czVxmqBXeClW8gxJBXCLpYjisXNR
>>> yXiDurakbeHG5FxrJEstYK9S2ZCM5uAx/aFy8PdT6rf7UO6XAi6nJ7xxQaMx4JMX
>>> XoA4oU1HsyOh8a0eg8NkmpMVJxeeZxr4DjlfLmXosMEpysG3d+mdq9SkKfKXGEsS
>>> t8PQqJDw8uLS+XdMmVLuwK6RtHV+ojNkH/FBQ6qfMGJEFWleeh2cKxiBoNTqOKlg
>>> sf9PznO/63HrswpeUJb8gfPs3tq7Mxa9DJzhgBc0U3toRg2VPjQTASXDc4PYqsJd
>>> K+WT/vbhpy34VDTABEPdD1DAxgit5H7AI+4DP6l5610qgWn1eNG6/jUi3mRIbojI
>>> S24/3udaFhOY/0NNDcI5mMijr77sjMbTSizO8ITabef/o9IiYkob32+0pW3j3+aO
>>> 0kK4SwWtoJ4qWwFsOD4ANcg5QjC9KcL2NlYe2gtWQhk3f9Fz9FbdfNzAptNvs94v
>>> qic2JONG9aa/CWnqO6RjF0JUCXIcUyr3jr5eKsBh9mli6wd3RYJbRZXHAXBD7ypA
>>> 3MPd2gX72zl6lCM+gJWgedK7c1YB6YbDcie+hGrj4m/0oHZeZdThbZJLymxvFRul
>>> 0gr9vxE99ggO3sTq9XLr
>>> =2y73
>>> -----END PGP SIGNATURE-----
>>>
>>>
>>
>>
>> --
>> Yo'av Moshe
>>
>
>
> --
> Yo'av Moshe
>
>
>
>
> >
>

-- 
Yo'av Moshe

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to