[ http://216.121.112.228/browse/NH-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Earl resolved NH-2533.
------------------------------
Resolution: Fixed
Fix Version/s: 3.2.0Beta1
There was divergent discussion on the mailing list about skip/take. The "SELECT" clause is not mandatory in hql, so I avoided the syntactically long route of "SELECT SKIP s TAKE t c FROM Class c". Since the majority of SQL dialects use the limit clause at the end, I decided to place SKIP and TAKE there instead of as a less conventional prefix. This incidentally made the implementation easier since the SELECT/FROM clause is still the root of the query, and the rest of the information is optionally attached to the query.
> Support paging in HQL
> ---------------------
>
> Key: NH-2533
> URL: http://216.121.112.228/browse/NH-2533
> Project: NHibernate
> Issue Type: New Feature
> Components: Core
> Affects Versions: 3.0.0.GA
> Reporter: Patrick Earl
> Assignee: Patrick Earl
> Priority: Minor
> Fix For: 3.2.0Beta1
>
>
> As per the discussion on the mailing list, this would add [SKIP x] [TAKE y] after the order by clause.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
