Hi all!
I have a few scenarios here that I believe are best solved without the
ORM overhead. For example, various log tables that do not require a
primary key, the rows are practically immutable, but are queried back
for statistical analysis. It is my understanding that I cannot use the
ORM
On Fri, Dec 16, 2011 at 2:55 PM, Vlad K. v...@haronmedia.com wrote:
Hi all!
I have a few scenarios here that I believe are best solved without the ORM
overhead. For example, various log tables that do not require a primary key,
the rows are practically immutable, but are queried back for
On Dec 16, 2011, at 3:55 PM, Vlad K. wrote:
Hi all!
I have a few scenarios here that I believe are best solved without the ORM
overhead. For example, various log tables that do not require a primary key,
the rows are practically immutable, but are queried back for statistical
So basically, if I'm understanding the docs correctly, and what you just
wrote:
Using the session object does not mean using the ORM. The ORM comes in
play with Mapper and Mapped instances, which in turn require a primary
key defined. So, I can use session.execute() to do non-ORM querying?
On Dec 16, 2011, at 7:32 PM, Vlad K. wrote:
So basically, if I'm understanding the docs correctly, and what you just
wrote:
Using the session object does not mean using the ORM.
more or lessthough if I wrote a program that had no ORM usage whatsoever
I'm not sure I'd have Session
