michal
Sat Apr 14 05:19:53 CDT 2007
will try the disconnected recordset, but i am already thinking of
switching back to mssql ;)
you dont have to be sorry :)) i just prefer the manipulation with the
recordset ...
- i never had performance issues
- dont have to care about the datatype (e.g. dml i need apostrophies
for string, etc.)
- the code looks nicer than some cryptic string concatination
anyway thats a pragmatic question and is not important here ... i will
play around and maybe discover the reason ... or maybe its just not
supported by the postgres provider ...
michal
On Apr 13, 10:44 pm, "Bob Barrows [MVP]" <reb01...@NOyahoo.SPAMcom>
wrote:
> michal wrote:
> > tried it with a the comandText but it ends up with the same error.
>
> Show the code: "commandText" looks fishy.
>
> > i know i could do it with DML but want to avoid this for several
> > reasons .. i like the way with the recordset but unfortunately it
> > makes problems with postgres. damn!
> > any other ideas?
>
> DML.,DML, DML ... oh, sorry.
> IMO, in ASP, recordsets should only be used to retrieve readonly data
> for display purposes. All data modifications should be done via DML.
> Since cursors (recordsets) are notoriously inefficient for data
> modifications, avoiding them increases the site's scalability.
>
> However, how about a disconnected client-side cursor instead of
> server-side:
>
> const adLockBatchOptimistic = 4
> set rs=createobject("adodb.recordset")
> rs.cursorlocation=3 'adUseClient
> rs.open "select <list of fields> from usr where 1=2",cn, _
> ,adLockBatchOptimistic ,1
>
> '
http://www.aspfaq.com/show.asp?id=2096
>
> set rs.activeconnection=nothing
> cn.close
> rs.addnew
> ...
> rs.update
> rs.addnew
> ...
> rs.update
> cn.open
> set rs.activeconnection=cn
> rs.updatebatch
> rs.close
> cn.close
>
> --
> Microsoft MVP -- ASP/ASP.NET
> Please reply to the newsgroup. The email account listed in my From
> header is my spam trap, so I don't check it very often. You will get a
> quicker response by posting to the newsgroup.