Recordset Object

Pros vs. Cons

[mattglet]

Can we start a discussion as to the Pros vs. Cons regarding the Recordset Object in classic ASP?

I don't use it, but I know people that swear by it. I feel that if you don't need a specific cursor, or don't need to page, then why use the extra overhead? Is the extra overhead even that significant?

Thanks for any examples/articles that can be given.

-Matt

[TheDave]

It's good for sorting

[TheNige]

I don't use it. I use GetRows so I can close my connection as soon as possible and then I can play with the data anyway that I wan't in my array.

Sorting can be done on the SQL call.

[TheDave]

TheNige, I'm aware of that, but did you know that the recordset object doesn't actually have to use a connection? You can create a recordset object, add fields to it, fill it with data and sort that data, all without going anywhere near a database.

[Easy_Coder]

TheDaVe -

When you state "fill it with data"... Where's that data coming from?

[TheDave]

It could be data the user provides, generated data, anything...

[duckhunter]

Things are a little different in ADO.NET. The DataSet and DataAdapter have somewhat replaced the GetRows function as it is not available.

Great example showing the two versions (Classic ASP & .NET)
[developerfusion.com ]

[TheNige]

TheDave: True, but I've never ran into a situation where I had that much data not coming from a database that need to be sorted or manipulated.

As Mentioned the same can be done with ASP.Net and the dataset...insert data from any source and manipulate it without touching a db.

[mattglet]

I realize the abilities in .NET, but I'm just dealing with classic ASP right now. No one is advocating the use of the RS object?

-Matt

[duckhunter]

I use the RS object all the time. Typically, the number of rows you will be pulling back for a single webpage or UI is small (less than 100 records and usually less than 15) The performance gains in GetRows with that amount of data doesn't even show up on the radar. Also, I prefer to work with the type-ahead help you get with the ADO objects, you won't get with the arrays.

Also, think about developers that might be working on your code in a few years. If you were picking up a piece of code for the first time and had to make some mods would you rather see myarray(1,1) or RS.Fields("OrderID")?
In my opinion the arrays make the code hard to read for the novice.

[TheDave]

Sorry I misunderstood the original question anyway. I thought you were just wondering what someone could possibly do with the recordset object. As a comparison between 2 methods, I cannot comment.