|
 |
asp_databases thread: ADO connection types
Message #1 by Chris Neale <Chris.Neale@s...> on Wed, 20 Sep 2000 14:27:19 +0100
|
|
If you're a careful programmer is there any reason to use adOpenForwardOnly?
Or adOpenStatic? As far as I can tell, these two connection types simply
limit your access to the dataset. A good thing for people new to it all, but
why would the more experienced programmer use such a thing? Does
adOpenstatic save memory by not opening write methods? Is it faster to use
ForwardOnly if I'm just dumping the contents of a database into a text file
for example? At the moment I have a tenancy to open things as adOpenKeyset.
Chris
Chaos! Panic! Disaster! (My work here is done)
Chris Neale. Web/Wap Developer
Chris.neale@s... <mailto:Chris.neale@s...>
www.sparkresponse.co.uk
Message #2 by ckoski@w... on Wed, 20 Sep 2000 09:55:21 -0400
|
|
adOpenForwardOnly is faster... less overhead and it gets the job done
quickly...
one uses the other types if they have specific needs to address... if
you're going to use the ADODB.Recordset object and do Update and AddNew and
other object oriented recordset manipulation operations, then you'd consider
using something other than adOpenForwardOnly... one is limited to the
functions you can use when you use adOpenForwardOnly, but a good programmer
can overcome most of the limitations by using other techniques...
Cory Koski
Web Programmer
Wabang Creative Technology and TBSource.com
e-certified as Master ASP programmer, Web programmer,
and IIS 4.0 Administrator
visit: http://www.tbsource.com/
(xxx) xxx-xxxx ext. 41
----- Original Message -----
From: "Chris Neale" <Chris.Neale@s...>
To: "ASP Databases" <asp_databases@p...>
Sent: Wednesday, September 20, 2000 9:27 AM
Subject: [asp_databases] ADO connection types
> If you're a careful programmer is there any reason to use
adOpenForwardOnly?
> Or adOpenStatic? As far as I can tell, these two connection types simply
> limit your access to the dataset. A good thing for people new to it all,
but
> why would the more experienced programmer use such a thing? Does
> adOpenstatic save memory by not opening write methods? Is it faster to use
> ForwardOnly if I'm just dumping the contents of a database into a text
file
> for example? At the moment I have a tenancy to open things as
adOpenKeyset.
>
> Chris
>
> Chaos! Panic! Disaster! (My work here is done)
> Chris Neale. Web/Wap Developer
> Chris.neale@s... <mailto:Chris.neale@s...>
> www.sparkresponse.co.uk
>
>
Message #3 by "Ken Schaefer" <ken@a...> on Thu, 21 Sep 2000 13:17:29 +1000
|
|
http://www.asptoday.com/articles/20000426.htm
covers using different cursors and locktypes.
An adOpenStatic cursor is about twice as expensive as an adOpenForwardOnly
cursor (depending on the number of records you are manipulating).
adOpenDynamic and adOpenKeyset are even more expensive.
Likewise locktypes other than adLockReadOnly are expensive as well.
Cheers
Ken
----- Original Message -----
From: "Chris Neale" <Chris.Neale@s...>
To: "ASP Databases" <asp_databases@p...>
Sent: Wednesday, September 20, 2000 11:27 PM
Subject: [asp_databases] ADO connection types
> If you're a careful programmer is there any reason to use
adOpenForwardOnly?
> Or adOpenStatic? As far as I can tell, these two connection types simply
> limit your access to the dataset. A good thing for people new to it all,
but
> why would the more experienced programmer use such a thing? Does
> adOpenstatic save memory by not opening write methods? Is it faster to use
> ForwardOnly if I'm just dumping the contents of a database into a text
file
> for example? At the moment I have a tenancy to open things as
adOpenKeyset.
>
> Chris
|
|
|
View Cart
