ADO.NET 2.0 Comings and goings

re: ADO.NET 2.0 Comings and goings

Jimmy Nilsson — Thu, 19 Aug 2004 06:26:00 GMT

Hi Jackie,

Ah, OK! Talk to you later!

Best Regards,
Jimmy
www.jnsk.se/weblog/
###

re: ADO.NET 2.0 Comings and goings

Jackie Goldstein — Thu, 19 Aug 2004 04:33:00 GMT

Jimmy,

Thanks for stopping by...

Of course, you are right about ObjectSpaces also being droppped - I guess I forgot to include them since I considered that "old" news that had already received alot of attention.

re: ADO.NET 2.0 Comings and goings

Jimmy Nilsson — Tue, 17 Aug 2004 22:34:00 GMT

Hi Jackie,

Long time, no see. I hope you are doing great!

I expected to see a mention about ObjectSpaces in this post when I read the header. What's your take on that?

Best Regards,
Jimmy
www.jnsk.se/weblog/
###

re: ADO.NET 2.0 Comings and goings

Jackie Goldstein — Mon, 16 Aug 2004 07:19:00 GMT

Tom,

You're obviously 100% correct on the current ASP.NET implementation of paging. I didn't think mention, because to me it was "obvious" that this was the way it worked, since I've known this for a long time. But, yeah, when I first realized it I was surprised and disappointed. The same goes for my students and clients - although they tend more to be disappointed and angry.

re: ADO.NET 2.0 Comings and goings

Jackie Goldstein — Mon, 16 Aug 2004 07:19:00 GMT

Alex,

I would tend to agree with you. I would prefer to have the choice (and responsibility) of choosing the right technology for teh task at end, rather than having it eliminated because it could easily be misused by others.

On the other hand, :-), as Niels points out, the feature is not totally eliminated - you just need to work a little harder to get to it and use it.

re: ADO.NET 2.0 Comings and goings

Alex Kazovic — Mon, 16 Aug 2004 06:10:00 GMT

Re server side cursors and scaling. There are many times when I have an application that I know does NOT need to scale to have 000's of users. Sometimes an application might just have a few users and will stay that way.

re: ADO.NET 2.0 Comings and goings

Eric Newton — Mon, 16 Aug 2004 06:07:00 GMT

Why does the ADO.NET team fell that typed datasets are the panacea for all data access? They're awful! They're constricting and most of the time FAIL for most types of XML documents...

The only thing I feel they are good at is prototyping a new app that will use caching and so forth, pretty much mitigating the so-called "benefit" of typing the datasets

And Kudos to tom, because I dont think a lot of people really understand that datagrid paging just throws out the rows that do not fit into the page.

Frankly, I'm continuing work on the server-side paging mechanism that I've built [http://www.ensoft-software.com/datacomponents/sqlpagedresultset]
(theres a major update in the works that will leverage Yukon's CLR in-proc runtime too]

re: ADO.NET 2.0 Comings and goings

Niels Berglund — Sun, 15 Aug 2004 18:40:00 GMT

As for point no 1: this is goodness IMO. If anyone really wants to use server side cursors, they can still use the underlying resource manager's cursor implementation.

re: ADO.NET 2.0 Comings and goings

Tom Pester — Sun, 15 Aug 2004 16:22:00 GMT

Why doesnt the sql server team add a limit clause to a query like this : select * from customers limit 50,10

This would give records 50 to 10.

The query optimizer could do some smart things I think and do it as efficient as possible.

Now we have to write lots of code on top and we do this over and over and over again.

For the poeple who dont know : if you use the default paging mechanism on the datagrid/dataview then *all* records will be transported to the client, not only your page (10 vs tablesize!). Am I correct on this one?

If you have a database server on a dedicated machine it spits out these huge ammounts of data over the wire :(

Pls Pls Pls by implementing this you would make the web more productive and the code written will be as efficient as possible. (mysql has it ;) , I dont know about oracle)

This is a good solution that we worked out :

http://www.codeproject.com/aspnet/PagingLarge.asp