On Fri, Oct 17, 2008 at 04:32:00PM -0700, Toshio Kuratomi wrote:
> Oleg Broytmann wrote:
> > On Fri, Oct 17, 2008 at 03:17:28PM -0700, Toshio Kuratomi wrote:
> >> +if MySQLdb.version_info[:3] >= (1, 2, 1) and
> >> MySQLdb.version_info[:3] < (1, 2, 2):
> >> +self.need_unicode =
On Mon, Oct 20, 2008 at 10:00:15AM -0700, Toshio Kuratomi wrote:
> So this patch makes the situation better with MySQL-python=1.2.1 but
> does not make it perfect. You could say that SQLObject simply does not
> work with MySQL-python <= 1.2.1 in lieu of this patch.
I see. Thank you very much!
Oleg Broytmann wrote:
> On Fri, Oct 17, 2008 at 04:32:00PM -0700, Toshio Kuratomi wrote:
>> Oleg Broytmann wrote:
>>>Another question: do I understand it right that MySQLdb *allows* unicode
>>> query strings but doesn't *require* them? Becasue my (humble and
>>> uninformed) opinion is to use th
On Fri, Oct 17, 2008 at 04:32:00PM -0700, Toshio Kuratomi wrote:
> Oleg Broytmann wrote:
> >Another question: do I understand it right that MySQLdb *allows* unicode
> > query strings but doesn't *require* them? Becasue my (humble and
> > uninformed) opinion is to use that "loophole" and do not
Oleg Broytmann wrote:
> On Fri, Oct 17, 2008 at 03:17:28PM -0700, Toshio Kuratomi wrote:
>> +if MySQLdb.version_info[:3] >= (1, 2, 1) and
>> MySQLdb.version_info[:3] < (1, 2, 2):
>> +self.need_unicode = True
>> +else:
>> +self.need_unicode = False
>
>Un
On Fri, Oct 17, 2008 at 03:17:28PM -0700, Toshio Kuratomi wrote:
> +if MySQLdb.version_info[:3] >= (1, 2, 1) and
> MySQLdb.version_info[:3] < (1, 2, 2):
> +self.need_unicode = True
> +else:
> +self.need_unicode = False
Unicode is required for MySQLdb 1.2
Oleg Broytmann wrote:
> On Fri, Oct 17, 2008 at 12:57:03PM -0700, Toshio Kuratomi wrote:
>> I looked at the SQLObject source and found that SQLObject used to change
>> the query into a byte string but that's no longer the case. The
>> relevant revisions are svn diff -r 3021:3022 which removes the
On Fri, Oct 17, 2008 at 12:57:03PM -0700, Toshio Kuratomi wrote:
> I looked at the SQLObject source and found that SQLObject used to change
> the query into a byte string but that's no longer the case. The
> relevant revisions are svn diff -r 3021:3022 which removes the
> functionality and the chu
We were having problems with SQLObject on our production Red Hat
Enterprise Linux 5 Servers but not on our development Fedora 9 boxes.
After some searching I tracked it down to a difference in the
MySQL-python modules. The RHEL5 boxes have MySQL-python-1.2.1 and the
Fedora boxes have 1.2.2. The 1
