|
From: Petr J. <pet...@tp...> - 2009-09-16 14:07:26
|
Hi, Working on the Firebird, I just wonder if exists some way how to push SQLObjects to configure kinterbasdb. I mean: I was able to use following snippet when I was working with the database directly (using kinterbasdb). import kinterbasdb kinterbasdb.init(type_conv=200) Is this possible using SQLObjects? Regards Petr |
|
From: Oleg B. <ph...@ph...> - 2009-09-16 14:19:14
|
On Wed, Sep 16, 2009 at 04:07:12PM +0200, Petr Jake?? wrote:
> Working on the Firebird, I just wonder if exists some way how to push
> SQLObjects to configure kinterbasdb.
>
> I mean: I was able to use following snippet when I was working with the
> database directly (using kinterbasdb).
>
> import kinterbasdb
> kinterbasdb.init(type_conv=200)
>
> Is this possible using SQLObjects?
You can use this in your program - this is module-level initialization;
when SQLObject does "import kinterbasdb" it gets already initialized
module. Or you can access connection.module after the connection has been
initialized if it's not too late.
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ ph...@ph...
Programmers don't die, they just GOSUB without RETURN.
|
|
From: Frank W. <fra...@no...> - 2009-09-16 14:59:36
|
i'm using sqlobject happily with interbase 7 via kinterbasdb.though not
directly but together with the turbogears framework.
connection uri is "interbase://user:pass@localhost
:3050//path/to/file.IB?debug=True"
it connects just fine
i then define my classes as usual (already existed in database):
class Teilnehmer(SQLObject):
class sqlmeta:
#fromDatabase=True # works more or less, but
# there's trouble with string
encodings
idName="NR"
cacheValues = True
BUCHUNGSNR = IntCol(dbName="BUCHUNGSNR")
NAME = StringCol(length=40, dbName="NAME")
HOTELCODE = StringCol(length=8, dbName="HOTELCODE")
...
finally i need some finetuning as the database doesn't have a charset
defined:
for each attribute/column:
def _get_NAME(self):
return self._SO_get_NAME() and unicode(self._SO_get_NAME(),
'iso-8859-1').strip() or u''
that's it.
finally u can use all the convenient magic that comes with SQLObj.
hth,
frank
2009/9/16 Petr Jakeš <pet...@tp...>
> Hi,
>
> Working on the Firebird, I just wonder if exists some way how to push
> SQLObjects to configure kinterbasdb.
>
> I mean: I was able to use following snippet when I was working with the
> database directly (using kinterbasdb).
>
> import kinterbasdb
> kinterbasdb.init(type_conv=200)
>
> Is this possible using SQLObjects?
>
> Regards
>
> Petr
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>
>
|
|
From: Oleg B. <ph...@ph...> - 2009-09-16 15:05:34
|
On Wed, Sep 16, 2009 at 04:59:00PM +0200, Frank Wagner wrote:
> NAME = StringCol(length=40, dbName="NAME")
>
> def _get_NAME(self):
> return self._SO_get_NAME() and unicode(self._SO_get_NAME(),
> 'iso-8859-1').strip() or u''
Frank, why don't you use UnicodeCol?
NAME = UnicodeCol(length=40, dbName="NAME", dbEncoding='iso-8859-1')
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ ph...@ph...
Programmers don't die, they just GOSUB without RETURN.
|
|
From: Frank W. <fra...@no...> - 2009-09-16 15:32:36
|
thanks for your suggestion Oleg! I will try that instead asap. but it's been some time ago when i wrote this thing, and afair i always had a lot of problems because the (legacy) database didn't have a charset declared at creation time (although it is de facto in iso-8859-1). so this was just the first working way that i could figure out. i guess the UnicodeCol doesn't do it in a very different way? greetings, frank 2009/9/16 Oleg Broytmann <ph...@ph...> > On Wed, Sep 16, 2009 at 04:59:00PM +0200, Frank Wagner wrote: > > NAME = StringCol(length=40, dbName="NAME") > > > > def _get_NAME(self): > > return self._SO_get_NAME() and unicode(self._SO_get_NAME(), > > 'iso-8859-1').strip() or u'' > > Frank, why don't you use UnicodeCol? > > NAME = UnicodeCol(length=40, dbName="NAME", dbEncoding='iso-8859-1') > > Oleg. > -- > Oleg Broytmann http://phd.pp.ru/ ph...@ph... > Programmers don't die, they just GOSUB without RETURN. > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > sqlobject-discuss mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss > |
|
From: Oleg B. <ph...@ph...> - 2009-09-16 15:58:37
|
On Wed, Sep 16, 2009 at 05:32:06PM +0200, Frank Wagner wrote:
> database didn't have a charset declared at creation time
> (although it is de facto in iso-8859-1).
> so this was just the first working way that i could figure out.
>
> i guess the UnicodeCol doesn't do it in a very different way?
> >
> > NAME = UnicodeCol(length=40, dbName="NAME", dbEncoding='iso-8859-1')
It uses a different implementation internally based on
validators/converters, but UnicodeValidator does exactly that - converts
strings from DB to unicode, and converts unicode to strings for DB. See
col.py.
BTW, speaking about validators...
> def _get_NAME(self):
> return self._SO_get_NAME() and unicode(self._SO_get_NAME(),
> 'iso-8859-1').strip() or u''
UnicodeCol only converts strings from/to unicode, so if you need
to strip and replace None's with u'' you have to do it yourself, but the
way to it, especially for many columns, is to create your own
validator/converter:
from col import validators
class StripValidator(validators.Validator):
def to_python(self, value, state):
if value is None:
return None # or u'' if you really want it
if isinstance(value, basestring):
return value.strip()
raise validators.Invalid("expected a str or unicode in column '%s', got %s %r instead" % \
(self.name, type(value), value), value, state)
And now you can use it in as many columns as you want:
NAME = UnicodeCol(length=40, dbName="NAME", dbEncoding='iso-8859-1',
validator=StripValidator(name="NAME"))
SURNAME = UnicodeCol(length=40, dbName="SURNAME", dbEncoding='iso-8859-1',
validator=StripValidator(name="SURNAME"))
SQLObject stacks validators so your validator will be used along with
UnicodeValidator in UnicodeCol, not instead of it.
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ ph...@ph...
Programmers don't die, they just GOSUB without RETURN.
|
