Michael Bayer wrote:
On Jul 30, 2007, at 4:58 PM, Jonathan LaCour wrote:
Michael Bayer wrote:
its a model taken from the way event loops usually work; any consumer
along the event chain is allowed to say, ive consumed the event and
stop further handlers from dealing with it. we can
Hello,
I'm realizing that I've been using .list() to query objects. But all the
examples in the docs talk about .all().
What's the difference ? Should I switch to .all() rather than .list() ?
Will list be deprecated in 0.4 ?
Regards,
--
Alexandre CONRAD
On 8/1/07, Alexandre CONRAD [EMAIL PROTECTED] wrote:
I'm realizing that I've been using .list() to query objects. But all the
examples in the docs talk about .all().
What's the difference ? Should I switch to .all() rather than .list() ?
Will list be deprecated in 0.4 ?
Exactly. list() is
Gaetan de Menten wrote:
What's the difference ? Should I switch to .all() rather than .list() ?
Will list be deprecated in 0.4 ?
Exactly. list() is the old way, all() is the 0.4 way.
Thanks Gaetan, I'll clean up my code to be compliant with 0.4.
Regards,
--
Alexandre CONRAD
jason kirtland wrote:
i think a name change is probably in order at the very least.
r3130 in the trunk implements a name change- EXT_CONTINUE will
propagate the hook to the next extension or back to the base
implementation. EXT_STOP will halt propagation.
it's only a name and doc change:
yes
Glauco wrote:
can someone read me?
Glauco
--
Alexandre CONRAD
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To
can someone read me?
Glauco
--
++
Glauco Uri - Programmatore
glauco(at)allevatori.com
Sfera Carta Software(r) [EMAIL
Right now, importing sqlalchemy on python 2.3 is broken. __name__ is
readonly in 2.3, so the import fails:
from sqlalchemy import *
Traceback (most recent call last):
File stdin, line 1, in ?
File /home/watsond/python_packages/sqlalchemy/__init__.py, line 9,
in ?
from sqlalchemy.schema
we currently dont have a right outer join. but this is not by
accident...theres really no use case for a right outer join, which
are more easily written as left outer joins.
some good articles on whats wrong with RIGHT outer join as well as
FULL outer join:
I have ORM mapped tables with a schema like the following:
---
Table 'users':
user_id integer
username text
balance integer
Table 'products':
product_id integer
cost integer
Table 'user_products':
user_id integer
product_id integer
---
when a user buys a product, I need to add a
On Aug 1, 2007, at 7:26 PM, Nick Johnson wrote:
I have ORM mapped tables with a schema like the following:
---
Table 'users':
user_id integer
username text
balance integer
Table 'products':
product_id integer
cost integer
Table 'user_products':
user_id integer
On Aug 1, 8:35 pm, Nick Johnson [EMAIL PROTECTED] wrote:
Thanks, I'll try that. Is there a way I can do this without locking,
though, such as by adding my own UPDATE query to the transaction?
uh sure probably with a MapperExtension that does an after_update()
for the User mapper...just
Hi,
I ran into an error trying to use two mappers for the same class. I
encounter the error AttributeError: type object 'MyObject' has no
attribute 'my_attribute'. Using the first mapper before creating the
other seems to corrupt the mapped class. Here is an example:
from sqlalchemy import *
On Aug 1, 9:45 pm, Gabriel Cote [EMAIL PROTECTED] wrote:
From what I understand of the documentation, I should be able to do
this using different entity names for the different mappers. Or is it
that once an object has been committed to the db using a certain
entity name, it can only be
14 matches
Mail list logo
