First of all thanks to all of you for your answers and time. Michael let me
say that I agree 100% with all you wrote and my will/wish is to work as you
wrote, but when you are inside the ORM its easy, other is if you want to
interact with the ORM from outside.
In my actual system I have more
Seems like you have a monumental problem to overcome. I'm glad you mentioned
EJB and have a Java background. In EJB, at least back when I used the very
early version 1.0, the concept of the transactional nature of various service
methods is defined separate from the implementation of the
On Thu, May 31, 2012 at 12:50 AM, Michael Bayer
mike...@zzzcomputing.com wrote:
Thing is, in order to work with a large volume of objects, you're
forced to do this, otherwise the session can grow uncontrollably.
flush periodically, and don't maintain references to things you're done with.
On May 31, 2012, at 10:35 AM, Claudio Freire wrote:
On Thu, May 31, 2012 at 12:50 AM, Michael Bayer
mike...@zzzcomputing.com wrote:
Thing is, in order to work with a large volume of objects, you're
forced to do this, otherwise the session can grow uncontrollably.
flush periodically, and
Hello all,
my curious situation is the following. A very simplified version of the
code is:
for data in res:
obj = MyObject()
---here I fill the obj, aventually doing some query (create session,
get, close) to SA
sess = createSession()
sess.add(obj)
sess.commit()
well yes, the way you're doing this is entirely the opposite of how the ORM is
designed to function.The Session has been developed in order to work in an
intelligent manner with full graphs of interrelated objects, all coordinated
under the umbrella of a transaction which applies atomicity
On Wed, May 30, 2012 at 8:39 PM, Michael Bayer mike...@zzzcomputing.com wrote:
well yes, the way you're doing this is entirely the opposite of how the ORM
is designed to function. The Session has been developed in order to work
in an intelligent manner with full graphs of interrelated
On May 30, 2012, at 8:53 PM, Claudio Freire wrote:
Thing is, in order to work with a large volume of objects, you're
forced to do this, otherwise the session can grow uncontrollably.
flush periodically, and don't maintain references to things you're done with.
The Session does not
