that error is being thrown by your DBAPI (database driver), since its  
an OperationalError.    so its something to do with your database  
configuration or the database-specific paramters you are sending it  
when you connect.


On May 21, 2007, at 3:44 AM, Jiang Sanyi wrote:

> The column is set to Unicode,why SQLAlchemy still can save a un- 
> unicode string, and now I cannot fetch this row.
>
> >>> show_q_a_all()
>
> Traceback (most recent call last):
>
>   File "<console>", line 1, in ?
>
>   File "D:\Riverleaf-Python2.4package\RiverSMS\cli\question.py",  
> line 6, in show
>
> _q_a_all
>
>     qs = model.Question.select()
>
>   File "build\bdist.win32\egg\sqlalchemy\ext\assignmapper.py", line  
> 7, in do
>
>   File "build\bdist.win32\egg\sqlalchemy\orm\query.py", line 301,  
> in select
>
>   File "build\bdist.win32\egg\sqlalchemy\orm\query.py", line 309,  
> in select_wher
>
> eclause
>
>   File "build\bdist.win32\egg\sqlalchemy\orm\query.py", line 798,  
> in _select_sta
>
> tement
>
>   File "build\bdist.win32\egg\sqlalchemy\orm\query.py", line 696,  
> in execute
>
>   File "build\bdist.win32\egg\sqlalchemy\orm\query.py", line 750,  
> in instances
>
>   File "build\bdist.win32\egg\sqlalchemy\engine\base.py", line 971,  
> in fetchall
>
> OperationalError: Could not decode to UTF-8 column  
> 'questions_headline' with tex
>
> t '为什么制定了MML的文档计划,今天却不去实施?'
>
>
>
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  姜三义 Jiang Sanyi HZ03952 81925609/13376819539(Free)
>
> Skype ID: amthree
>
> 三义定律:工作没做好 Sanyi Rule: Work not well done
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
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