Hello all,

I'm using SQL SERVER native SQL to do my paginations in my system.

There are just few SQL that I'm putting inside a Store procedure..

I would like to remove them from there because I dont want take care of SQL outside NHibernate /C# code.

How can I remove my SQL to do that?

Remember that the approach that I'm doing doesn't select all records in the database...

I select just those records that I need according to current page and the amount of records by page.

thanks!

people..

I took a look at internet by googling and I found something that does exactly what I was needing



where "RecordsByPage" and "firstRercodToShow" are information came from aspx code behind page..


So, I dont know how NHibernate does the pagination yet

I dont know if it retrieves all records and just filters them or really does as should be...by retrieving just the ones that I have passed via parameter

but it works fine!

[/code]

The answer is, it depends.

MySQL supports setting skipping records and setting max records to be retrieved, so NHibernate will only get those records as MySQL will skip the first records as requested.

On the other hand, SQL Server 2000 supports setting max records but doesn't support skipping to the first specified, so it can't skip the records like MySQL can. As a result NHibernate still gets the skipped records in the result set but just doesn't create objects from them.

It's done in the most efficient way possible given the technology it works with, but it will depend on your RDBMS.

Cheers,

Symon.

exactly.

but there is a way to do that by using SQL SERVER that doesn't retrieve all records in the database.

it would be by using temp table in a Store Procedure where you could pass the current page and how many records you want to get.

In MySQL that would be so easy by using LIMIT, so NHibernate can do it easily as well

but I'm not sure if inside NHibernate it would be doing something similar that I do in my stored procedure with temp tables...

It's not. NHibernate just uses the underlying database's limit and top keyword-equivalents as far as I know.

Cheers,

Symon.