Fwd: Re: [Glorp-development] 'Dirty' queries

Date: Wed, 13 Dec 2006 14:15:00 +0100
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Glorp-development] 'Dirty' queries
Thread-Index: AccetpI/UWdIdI9FQJ6uQLZf1cVizwAAXb7Q
From: "Mark Plas" <[hidden email]>
To: "Antony Blakey" <[hidden email]>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Linux/GNU) at net7.be
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
        See http://spamassassin.org/tag/ for more details.
        Report problems to
         http://sf.net/tracker/?func=add&group_id=1&atid=200001
        1.0 FORGED_RCVD_HELO       Received: contains a forged HELO
Cc: [hidden email]
Subject: Re: [Glorp-development] 'Dirty' queries
X-BeenThere: [hidden email]
X-Mailman-Version: 2.1.8
List-Id: <glorp-development.lists.sourceforge.net>
List-Unsubscribe: < https://lists.sourceforge.net/lists/listinfo/glorp-development >,
         <[hidden email] >
List-Archive: < http://sourceforge.net/mailarchive/forum.php?forum=glorp-development >
List-Post: <[hidden email]>
List-Help: <[hidden email] >
List-Subscribe: < https://lists.sourceforge.net/lists/listinfo/glorp-development >,
         <[hidden email] >
Sender: [hidden email]
X-pstn-levels:     (S:99.90000/99.90000 R:95.9108 P:95.9108 M:97.0282 C:98.6951 )

Hi Antony,

Just to be sure, if you do
- commitUnitOfWork
- query
- rollback transaction
- commitUnitOfWork
- commit transaction

Will the changes you made in the unitOfWork be committed ? Or does the
unitOfWork 'forget' its changes after you do a commitUnitOfWork ?
I'd like to be able to start a unit of work, perform some queries that
require the state of the session and eventually commit the entire
unitOfWork.

Thanks,
Mark

-----Original Message-----
From: [hidden email]
[[hidden email]] On Behalf Of
Antony Blakey
Sent: woensdag 13 december 2006 13:52
To: Mark Plas
Cc: [hidden email]
Subject: Re: [Glorp-development] 'Dirty' queries


On 13/12/2006, at 8:29 PM, Mark Plas wrote:

> My question: Do you think it would be difficult to put this kind of 
> behavior in Glorp? Perhaps via an extra parameter on a Query object 
> to tell Glorp to temporarily flush its changes ?
Glorp has two separate delimiters: the transaction and the unit of 
work. I start a transaction and a unit of work, and then, before 
doing a query which needs the in-memory changes, do a session 
commitUnitOfWork which actually writes the changes to the database. I 
can do as many commitUnitOfWork's as I wish within the transaction. 
Finally I commit/rollback the transaction.

I've only been using Glorp for a month, so that's not a complete 
explanation, but I think it answers your direct question.

Antony Blakey
--------------------------
CTO, Linkuistics Pty Ltd
Ph: 0438 840 787

75% of statistics are made up on the spot.



------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V
_______________________________________________
Glorp-development mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/glorp-development

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Glorp-development mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/glorp-development