On Tue, Sep 12, 2006 at 03:17:55PM +0200, Markus Gritsch wrote:
> But I'm sure my original
> statement didn't offend you too much
Not at all.
> since it contained a big wink at
> the end :D
Sure, I saw it. :)
On the serious side: thank you for the help and explanations!
Oleg.
--
On 9/12/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 12, 2006 at 01:19:30PM +0200, Markus Gritsch wrote:
> > > I don't use MySQL, so I have to rely on patches form other
> > >people. You can add your ones. ;)
> >
> > Sounds a bit frightening to me
>
>Should I run all the backen
On Tue, Sep 12, 2006 at 01:19:30PM +0200, Markus Gritsch wrote:
> > I don't use MySQL, so I have to rely on patches form other
> >people. You can add your ones. ;)
>
> Sounds a bit frightening to me
Should I run all the backends SQLObject can connect to? Firebird, MaxDB?
Should I buy a perso
On 9/12/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
>But can one use use_unicode=0 to require MySQLdb to return non-unicode
> strings?
>From reading the paragraph describing this keyword-parameter at
http://sourceforge.net/docman/display_doc.php?docid=32071&group_id=22307#functions-and-attri
On Tue, Sep 12, 2006 at 11:44:53AM +0200, Markus Gritsch wrote:
> >and output (SELECT)?
>
> I think by specifying use_unicode=1 in the connection one can require
> that all results are returned as unicode.
But can one use use_unicode=0 to require MySQLdb to return non-unicode
strings?
> I won
On 9/11/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
> PS. BTW, you seems to know MySQLdb (MySQL-python) good.
Don't let yourself be fooled ;) I only stumbled across some things
while I made my app working with MySQL.
> Can you say how I can prevent MySQLdb from using unicode on input
> (INSERT
On Mon, Sep 11, 2006 at 09:53:25PM +0200, Markus Gritsch wrote:
> Everything works fine when using an SQLite connection
A bug in SQLite, PySQLite or SQLiteConnection? Postgres (or psycopg)
does not allow unicode.
>if self.need_unicode:
> into
>if self.need_unicode and not isinstance(qu
On 9/11/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 11, 2006 at 09:26:43PM +0200, Markus Gritsch wrote:
> > one issue remains: When doing a select() using LIKE (maybe with other
> > SQLBuilder objects too) with a unicode string, one gets a traceback,
> [skip]
> > print Test.select(L
On Mon, Sep 11, 2006 at 09:26:43PM +0200, Markus Gritsch wrote:
> one issue remains: When doing a select() using LIKE (maybe with other
> SQLBuilder objects too) with a unicode string, one gets a traceback,
[skip]
> print Test.select(LIKE(Test.q.name, name))[0].name.encode('utf-8') #
Please re
Hi,
one issue remains: When doing a select() using LIKE (maybe with other
SQLBuilder objects too) with a unicode string, one gets a traceback,
because the type of the variable query in
myquery = unicode(query, self.encoding)
in mysqlconnection.py is instead of . So
either SQLBuilder has to b
Hi,
I think I found the solution. The trick is to specify both, the
charset and the sqlobject_encoding as parameters in the connection
URI: ?use_unicode=1&charset=utf8&sqlobject_encoding=utf-8
By using this, the following example works fine. The data in the DB
is also stored in the desired (ut
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
19 matches
Mail list logo
