WilsonORMapper v4.2.1 Released -- Includes Sql2005 Row_Number Paging

Wednesday, January 25, 2006

Update: WilsonORMapper v4.2.1.0 (1/24/2006) includes the following:

Sql2005 Provider for Efficient Paging with Row_Number
More Lookup cases using Outer Join now Supported
ObjectQuery has SkipCounts option for Performance
Multiple optimizations with the help of Marc Brooks

Marc Brooks also provided the following new features:

Auto keyType can be Composite with the last being Auto
DefaultNamespace can be defined in each mapping file
DateTime provider-specific min/max for db compatibility

Bug-Fix: Non-Lazy-Loaded Generic (v2.0) Collections
Bug-Fix: Transactions with specified IsolationLevel
Bug-Fix: Empty Byte Arrays work with nullValue="[]"
Bug-Fix: A few OPath fixes included by Jeff Lanning

CodeSmith: Another set of Templates, by Jason Bunting

I would also like to say a great big THANK YOU to some other unnamed people that just go out of their way to help me, whether it be a simple but personal note of appreciation, an extra monetary donation, or help with extending the code and testing things -- you know who you are. I would also like to say THANK YOU to my current client for allowing me to work on some of my own projects at times, and for right now being so very understanding and appreciative of the many extra hours I've put in that have really added up here lately.

9 Comments

Oh man, play time tomarrow! Nice work Paul, can't wait to play with this.

Travis - Wednesday, January 25, 2006 5:13:00 AM

Outstanding, Paul! Thank you for your continued support and commitment, as well as a big thanks to all those who have contributed. WilsonORMapper is a brilliant tool.

David - Wednesday, January 25, 2006 5:32:00 AM

"Efficient Paging with Row_Number"???

Looking at the execution plan it doesn't seem efficient(at least according to my tests). if you select pageindex 100 with pagesize 10 out of a 10000 rows table, guess how many rows does the sql server scan?

Br,

Deyan Petrov

Deyan Petrov - Wednesday, January 25, 2006 9:13:00 AM

You or your DBA are still responsible for proper database indexing. O/R Mappers do NOT remove the need for database optimization -- they free your team from boring CRUD so that they can focus their time where it should be spent.

Paul Wilson - Wednesday, January 25, 2006 11:23:00 AM

How would you index the dynamically ROW_NUMBER generated column?? Because afterall it gets down to this, when you want to filter out 1 page out of the 100 pages resultset ... Or you mean the 100 pages resultset should have been narrowed down before doing the ROW_NUMBER to 1 page using other indexes??

Deyan Petrov - Thursday, January 26, 2006 10:06:00 AM

The ROW_NUMBER column shouldn't be the problem, at least I don't think so anyhow. The problem you are seeing is most likely the ORDER BY clause, and if you have a WHERE clause then it too possibly.

Paul Wilson - Thursday, January 26, 2006 12:12:00 PM

Congratulations on shipping a new version Paul!

Wallym - Thursday, January 26, 2006 5:32:00 PM

How do you use a variable in the order by clause of the row_number() function?

Hong - Wednesday, February 1, 2006 5:29:00 PM

I don't use a variable for that -- O/R Mappers produce dynamic sql, some of it parameterized and some of it not.

Paul Wilson - Wednesday, February 1, 2006 5:56:00 PM

Comments have been disabled for this content.