|
From: Carlos R. <car...@gm...> - 2004-12-14 00:59:28
|
Hello all,
I'm trying to use a fairly complex query with SQLObject, and was
having a problem with a "AssertionError: Database None unknown" error
message. I've traced it down to this:
class Catalog(SQLObject):
item_code = StrCol(length=15, notNone=True, alternateID=True)
item_descr = StrCol(length=40, default='')
print Catalog.q.item_code == 1 # works!
print Catalog.q.item_code == '001' # does not work!
cribeiro@fiona:~/work/c-l-py $ python test-select-sql-object.py
(catalog.item_code = 1)
Traceback (most recent call last):
File "test-select-sql-object.py", line 15, in ?
print Catalog.q.item_code == '001'
File "/usr/lib/python2.3/site-packages/sqlobject/sqlbuilder.py",
line 157, in __str__
return self.__sqlrepr__(None)
File "/usr/lib/python2.3/site-packages/sqlobject/sqlbuilder.py",
line 222, in __sqlrepr__
return "(%s %s %s)" % (sqlrepr(self.expr1, db), self.op,
sqlrepr(self.expr2, db))
File "/usr/lib/python2.3/site-packages/sqlobject/converters.py",
line 187, in sqlrepr
return converter(obj, db)
File "/usr/lib/python2.3/site-packages/sqlobject/converters.py",
line 98, in StringLikeConverter
assert 0, "Database %s unknown" % db
AssertionError: Database None unknown
That's a strange bug, because it's failing for a really simple query
(almost identical to the one in the tutorial for SQLObject). I'm using
the latest SVN code. It does not matter if StrCol is a UnicodeCol or
StringCol. It's strange because it works for ints, but doesn't work
when the argument is a string. I'm trying to trace it down, but that's
the first time I'm trying to understand SQLBuilder internals, so I
thought that it would be good to report it.
--
Carlos Ribeiro
Consultoria em Projetos
blog: http://rascunhosrotos.blogspot.com
blog: http://pythonnotes.blogspot.com
mail: car...@gm...
mail: car...@ya...
|
|
From: Carlos R. <car...@gm...> - 2004-12-14 00:59:55
|
Hello all, I'm trying to use a fairly complex query with SQLObject, and was having a problem with a "AssertionError: Database None unknown" error message. I've traced it down to this: class Catalog(SQLObject): item_code = StrCol(length=15, notNone=True, alternateID=True) item_descr = StrCol(length=40, default='') print Catalog.q.item_code == 1 # works! print Catalog.q.item_code == '001' # does not work! cribeiro@fiona:~/work/c-l-py $ python test-select-sql-object.py (catalog.item_code = 1) Traceback (most recent call last): File "test-select-sql-object.py", line 15, in ? print Catalog.q.item_code == '001' File "/usr/lib/python2.3/site-packages/sqlobject/sqlbuilder.py", line 157, in __str__ return self.__sqlrepr__(None) File "/usr/lib/python2.3/site-packages/sqlobject/sqlbuilder.py", line 222, in __sqlrepr__ return "(%s %s %s)" % (sqlrepr(self.expr1, db), self.op, sqlrepr(self.expr2, db)) File "/usr/lib/python2.3/site-packages/sqlobject/converters.py", line 187, in sqlrepr return converter(obj, db) File "/usr/lib/python2.3/site-packages/sqlobject/converters.py", line 98, in StringLikeConverter assert 0, "Database %s unknown" % db AssertionError: Database None unknown That's a strange bug, because it's failing for a really simple query (almost identical to the one in the tutorial for SQLObject). I'm using the latest SVN code. It does not matter if StrCol is a UnicodeCol or StringCol. It's strange because it works for ints, but doesn't work when the argument is a string. I'm trying to trace it down, but that's the first time I'm trying to understand SQLBuilder internals, so I thought that it would be good to report it. -- Carlos Ribeiro Consultoria em Projetos blog: http://rascunhosrotos.blogspot.com blog: http://pythonnotes.blogspot.com mail: car...@gm... mail: car...@ya... |
|
From: Carlos R. <car...@gm...> - 2004-12-14 01:40:47
|
On Mon, 13 Dec 2004 22:59:52 -0200, Carlos Ribeiro <car...@gm...> wrote:
> I'm trying to trace it down, but that's
> the first time I'm trying to understand SQLBuilder internals, so I
> thought that it would be good to report it.
I think I'm beginning to understand how do SQLBuilder works, but
still, I have no idea on how to solve this problem. The SQLExpression
class has this code:
def __str__(self):
return self.__sqlrepr__(None)
That's the code that is called, and it passes None as the db, in this
case. But the StringLikeConverter (that is the converter that it finds
in the registry for a constant string) expects a valid db name:
def StringLikeConverter(value, db):
if db in ('mysql', 'postgres'):
for orig, repl in sqlStringReplace:
value = value.replace(orig, repl)
elif db in ('sqlite', 'firebird', 'sybase', 'maxdb'):
value = value.replace("'", "''")
else:
assert 0, "Database %s unknown" % db
return "'%s'" % value
And that's where the assertion happens. What can I do in this case?
I'm really lost and looking for ideas :-) I could possibly initialize
the SQLExpression object with a valid db name (borrowed from the best
possible candidate it finds while building the expression), but I'm
not sure about the side effects.
--
Carlos Ribeiro
Consultoria em Projetos
blog: http://rascunhosrotos.blogspot.com
blog: http://pythonnotes.blogspot.com
mail: car...@gm...
mail: car...@ya...
|
|
From: Ian B. <ia...@co...> - 2004-12-14 01:47:03
|
Carlos Ribeiro wrote:
> On Mon, 13 Dec 2004 22:59:52 -0200, Carlos Ribeiro <car...@gm...> wrote:
>
>>I'm trying to trace it down, but that's
>>the first time I'm trying to understand SQLBuilder internals, so I
>>thought that it would be good to report it.
>
>
> I think I'm beginning to understand how do SQLBuilder works, but
> still, I have no idea on how to solve this problem. The SQLExpression
> class has this code:
>
> def __str__(self):
> return self.__sqlrepr__(None)
>
> That's the code that is called, and it passes None as the db, in this
> case. But the StringLikeConverter (that is the converter that it finds
> in the registry for a constant string) expects a valid db name:
>
> def StringLikeConverter(value, db):
> if db in ('mysql', 'postgres'):
> for orig, repl in sqlStringReplace:
> value = value.replace(orig, repl)
> elif db in ('sqlite', 'firebird', 'sybase', 'maxdb'):
> value = value.replace("'", "''")
> else:
> assert 0, "Database %s unknown" % db
> return "'%s'" % value
>
> And that's where the assertion happens. What can I do in this case?
> I'm really lost and looking for ideas :-) I could possibly initialize
> the SQLExpression object with a valid db name (borrowed from the best
> possible candidate it finds while building the expression), but I'm
> not sure about the side effects.
SQLObject can't generate SQL without knowing what database it is
generating SQL for -- in this case, particularly strings. So you could do:
print Catalog.sqlrepr(Catalog.q.item == '001')
This calls sqlrepr(Catalog.q.item == '001', Catalog._connection.dbname)
or something like that.
--
Ian Bicking / ia...@co... / http://blog.ianbicking.org
|
|
From: Carlos R. <car...@gm...> - 2004-12-14 02:30:57
|
On Mon, 13 Dec 2004 19:47:09 -0600, Ian Bicking <ia...@co...> wrote:
> SQLObject can't generate SQL without knowing what database it is
> generating SQL for -- in this case, particularly strings. So you could do:
I'm curious now. This is an example quoted in the SQLBuilder doc:
>>> person.first_name == 'John'
person.first_name = 'John'
In this case, how does it know how to quote the string? (or, in other
words, does this example still work?)
> print Catalog.sqlrepr(Catalog.q.item == '001')
>
> This calls sqlrepr(Catalog.q.item == '001', Catalog._connection.dbname)
> or something like that.
If the expression on the left side is attached to a db, I think that
it could use this information to format the term on the right side.
For example:
def __eq__(self, other):
if other is None:
return ISNULL(self)
else:
return SQLOp("=", self, other)
On the call to SQLOp("=", self, other), a wrapper could be provided
for the "other" term that would fill the db information. Something
like this:
def __eq__(self, other):
if other is None:
return ISNULL(self)
else:
return SQLOp("=", self, default_db_wrapper(other, self.db))
Anyway, it's now to late to even start looking at it today. I've
solved my problem partially by writing the queries manually, but I
would like to be able to use SQLBuilder too keep the code cleaner &
more db independent.
--
Carlos Ribeiro
Consultoria em Projetos
blog: http://rascunhosrotos.blogspot.com
blog: http://pythonnotes.blogspot.com
mail: car...@gm...
mail: car...@ya...
|
|
From: Sam N. <sa...@se...> - 2004-12-19 00:26:05
|
Hello,
I am new to sqlobject, and i'm finding it to be a truly wonderful layer
and model. I have had some problems with RelatedJoin attributes and I
have seen some talk of that recently on the list. The suggestion to
explicitly define joinColumn, otherColumn, and joinMethodName solved a
few different problems that I was having.
Unsolved Problems - I have pasted my 'Group' class below. If I do a
dir(Group), I see attributes for 'admins' 'users' and more. I also see
the methods 'addUser' and 'removeUser', *but* there are no corresponding
'addAdmin' and 'removeAdmin' methods!
I have gathered from the list that the current revision in subversion
solves some of these problems but may not solve all of them. I am not
familiar with the state of development, so I want to ask, should I
update to the newest revision? Is it more stable and less buggy than v.6?
Can anyone help with info about my problem? If the consensus is to
update to a newer sqlobject, then I will do so and report back.
Thanks for any help!
- Sam Nilsson
from sqlobject import *
from Store import conn
class Group(SQLObject):
_table = "group_table"
_connection = conn
name = StringCol()
description = StringCol()
users = RelatedJoin("User",
intermediateTable='group_table_user', joinColumn='group_table_id',
otherColumn='user_id', joinMethodName='users')
admins = RelatedJoin("User",
intermediateTable='group_table_admin', joinColumn='group_table_id',
otherColumn='user_id', joinMethodName='admins')
categories = MultipleJoin("Category", joinColumn='group_id',
joinMethodName='categories')
|
