Hi,
Currently sqlboject uses LIKE for all its comparisons which is case sensitive
in some databases (eg. postgres) (I _think_ this is standard compliant, im on
the road currently, so i cant check) others do not (eg mysql).
At least I sometimes need a case sensitive LIKE and sometimes not. Is the
On 9/10/06, paul kölle <[EMAIL PROTECTED]> wrote:
> Markus Gritsch schrieb:
> > On 9/10/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
> >> On Sun, Sep 10, 2006 at 02:41:02PM +0200, Markus Gritsch wrote:
> >> > The following code worked in SQLObject-0.7.1b1 but raises an exception
> >> > when with S
On 9/10/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
> On Sun, Sep 10, 2006 at 04:16:12PM +0200, Markus Gritsch wrote:
> > col.py:
> >
> > class UnicodeStringValidator(validators.Validator):
> >
> >def to_python(self, value, state):
> >if value is None:
> >return None
> >
On Sun, Sep 10, 2006 at 04:16:12PM +0200, Markus Gritsch wrote:
> col.py:
>
> class UnicodeStringValidator(validators.Validator):
>
>def to_python(self, value, state):
>if value is None:
>return None
>if isinstance(value, unicode):
>return value
>
On 9/10/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
> On Sun, Sep 10, 2006 at 03:29:22PM +0200, Markus Gritsch wrote:
> > >> # -*- coding: latin-1 -*-
> [skip]
> >return codecs.utf_8_decode(input, errors, True)
> > UnicodeDecodeError: 'utf8' codec can't decode bytes in position 3-4:
> > unexp
Markus Gritsch schrieb:
> On 9/10/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
>> On Sun, Sep 10, 2006 at 02:41:02PM +0200, Markus Gritsch wrote:
>> > The following code worked in SQLObject-0.7.1b1 but raises an exception
>> > when with SQLObject-0.7.1rc1:
>> >
>> > # -*- coding: latin-1 -*-
>> >
On Sun, Sep 10, 2006 at 03:29:22PM +0200, Markus Gritsch wrote:
> >> # -*- coding: latin-1 -*-
[skip]
>return codecs.utf_8_decode(input, errors, True)
> UnicodeDecodeError: 'utf8' codec can't decode bytes in position 3-4:
> unexpected end of data
This is why I always recommend against u'' s
On 9/10/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
On Sun, Sep 10, 2006 at 02:41:02PM +0200, Markus Gritsch wrote:
> The following code worked in SQLObject-0.7.1b1 but raises an exception
> when with SQLObject-0.7.1rc1:
>
> # -*- coding: latin-1 -*-
>
> from sqlobject import *
>
> sqlhub.proce
On Sun, Sep 10, 2006 at 02:41:02PM +0200, Markus Gritsch wrote:
> The following code worked in SQLObject-0.7.1b1 but raises an exception
> when with SQLObject-0.7.1rc1:
>
> # -*- coding: latin-1 -*-
>
> from sqlobject import *
>
> sqlhub.processConnection = connectionForURI('mysql://[EMAIL PROTE
Hi,
I am using MySQL-python.exe-1.2.2b1.win32-py2.4.exe.
The following code worked in SQLObject-0.7.1b1 but raises an exception
when with SQLObject-0.7.1rc1:
# -*- coding: latin-1 -*-
from sqlobject import *
sqlhub.processConnection = connectionForURI('mysql://[EMAIL PROTECTED]/test')
class
On Sun, Sep 10, 2006 at 01:26:46PM +0200, Michel Albert wrote:
> The question: Is there a way to explicitly tell sqlobject the constraint
> name (like you do with the sequence-name with _idSequence)
There is no.
Oleg.
--
Oleg Broytmannhttp://phd.pp.ru/[EMAIL PRO
Hi again,
I found another small problem when working with a database with mixed case
columns. This one deals with foreign keys. Here is the portion of
sqlobject that generates the error (line 751 of col.py). Another
occurrence is on line 776.
class SOForeignKey(SOKeyCol):
def __
12 matches
Mail list logo
