Alex Le Dain wrote:
> I am interested in why was this was done, because I cannot see it from
> my perspective. Is there a deeper rationale here?
My apologies, I went to the source and have nutted it out. It appears
that the MySQLdb layer requires unicode for versions > 1.2.1. In
upgrading SQLObject I also upgraded the MySQLdb layer and hence the
problem sprang into being!
Still don't understand why encoding etc enough to understand what's
required at my end to allow characters 128..255 into a StringCol(). If
someone could point this out that would be great.
> Secondly, I am progressing towards migrating to 0.9.x as fast as I can.
> Does the same check exist in 0.9.x?
I am guessing it would :-)
Alexander C. Le Dain, PhD