On 12/9/06, jose [EMAIL PROTECTED] wrote:
Thank you Michael for your explanation.
Since I can do (on sqlalchemy), the same thing in more than one ways,
I'm very confused and I would like ask you, about
Constructing SQL Queries via _table objects_ or _mapper classes_
Seems to me that
it should be noted that SQLAlchemy is really *two* separate software
packages in one.
one part of SA is, a tool that allows you to build SQL queries through
python expressions. I usually call it the SQL construction part of
SA. you issue SQL statements and get back result sets, which act like
Robin Munn wrote:
On 12/9/06, jose [EMAIL PROTECTED] wrote:
Thank you Michael for your explanation.
Since I can do (on sqlalchemy), the same thing in more than one ways,
I'm very confused and I would like ask you, about
Constructing SQL Queries via _table objects_ or _mapper classes_
Seems
when SA was first released, someone immediately suggested that the
identity map of Session be weak referencing, which appeared to be an
obvious improvement, so that you could load as many objects as you want
from the session and whatever you didnt use would just go away. but
now it
Sorry, I had checked the docs but not the FAQ. I opened a ticket as well,
feel free to close it. I think it should be stated in a more clear in way in
the docs, though, since it's an unpredictable behaviour.
But was that behaviour present in 0.1.x? I feel a bit estranged about never
noticing
