From: Marc Saric <marc.saric@gm...> - 2004-11-09 14:00:12
-----BEGIN PGP SIGNED MESSAGE-----
due to the fact, that I got no response to my previous mail "Problem
with longID = True and sequences" from 2004-11-04 I did some more
testing regarding this problem:
I use SQLObject 0.6, PostgreSQL 7.4.2, Python 2.3.3, psycopg 1.1.14 on
SuSE Linux 9.1.
I have prepared the following little sample, which does or does not work
depending on where you define longID = True:
#! /usr/bin/env python
from sqlobject import *
__connection__ = PostgresConnection(
~ host='localhost', db='sqlobject_test',
~ user='YourUserName', passwd='', debug = 1)
# FIXME: This does not work (but it should?)
#__connection__.style = MixedCaseUnderscoreStyle(longID = True)
~ # This does work, where's the difference?
~ _style = MixedCaseUnderscoreStyle(longID = True)
~ testEntry = StringCol()
t2 = TestTable2(
~ testEntry = "bla"
According to the documentation, __connection__.style =
MixedCaseUnderscoreStyle(longID = True) should also work (globaly) but
it does not (longID is obviously ignored).
Can anyone reproduce the failure (just cut & paste and uncomment the
__connection__-line and comment the _style-line).
Is this a bug or am I doing something stupid here?
Any answer would be appreciated.
Marc Saric http://www.marcsaric.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
From: Carlos Ribeiro <carribeiro@gm...> - 2004-11-09 16:04:52
On Tue, 09 Nov 2004 14:59:57 +0100, Marc Saric <marc.saric@...> wrote:
> Can anyone reproduce the failure (just cut & paste and uncomment the
> __connection__-line and comment the _style-line).
> Is this a bug or am I doing something stupid here?
> Any answer would be appreciated.
(this is an answer but I'm not sure if it will be appreciated...)
I've *not* tested it. However, I was wondering if it couldn't be
caused by some interaction with PostgreSQL, or the PostgreSQL driver,
due either to a bug or to some limitation on naming (which differs a
lot between DBs). What leads to another question, did you test it with
another (different) database engine? It may help to reduce the problem
Consultoria em Projetos