On Mon, Jan 07, 2008 at 01:00:20AM -0200, Marcos Dione wrote:
until yesterday did worked, but seems like after I upgraded to the
new sqla 0.4.2-1 from Debian Sid, it broke this way. am I doing anything
conceptually wrong?
--
$ sqlite3 test.sqlt
SQLite version 3.4.2
Enter .help
On Mon, Jan 07, 2008 at 03:41:22PM -0200, Marcos Dione wrote:
On Mon, Jan 07, 2008 at 01:00:20AM -0200, Marcos Dione wrote:
class SQLAObject (object):
def __init__ (self, **kwargs):
object.__init__ (self)
self.__dict__.update (kwargs)
I got this in IRC:
01
me and my now ex-girlfriend just broke...
sorry, couldn't help myself. it's just that I've been the whole
afternoon chasing this bug in #sqlalchemy. see the attached script. it
basically creates a Feed and a Post related with that Feed. the Feed
goes just fine in the db, but the Post
hi all. I've been using sqlalchemy in one of may projects. I
followed the steps in http://www.sqlalchemy.org/trac/wiki/WhatsNewIn04,
but the I got this backtrace:
Traceback (most recent call last):
File ./kress.py, line 664, in ?
main(sys.argv)
File ./kress.py, line 658, in main
hi, I'm rather new to SQLAlchemy, using version 0.3.x right now. I
would like to know the reason why Query.filter() returns another Query
object instead of aplying in place, if there is one. an answer to this
would help me to understand better this ORM.