Re: Is there ever a reason to have a transaction around a select...
- From: "Miha Markic [MVP C#]" <miha at rthand com>
- Date: Sun, 1 Apr 2007 11:47:07 +0200
It depends on your requirements but usually there is no need for (explicit) transaction.
--
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/
"David Thielen" <thielen@xxxxxxxxxxxxx> wrote in message news:88DB2D9D-01F6-403F-93AF-1CABC892247B@xxxxxxxxxxxxxxxx
1) that will always return 0 or 1 rows?
2) that will retun N rows?
In each case where the results will be displayed to the user and so there
can be changes that occur to the DB after the select completes.
--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
.
- Prev by Date: Re: Is there ever a reason to have a transaction around a select...
- Next by Date: RE: GAC
- Previous by thread: Re: Is there ever a reason to have a transaction around a select...
- Next by thread: Re: Is there ever a reason to have a transaction around a select..
- Index(es):
Relevant Pages
|
