If this is really important you could map a read only property on your entity with custom sql for that property. Do an ISNULL(prop,date(...)) etc. Clunky but it would work.
On Mar 10, 2009 10:21 AM, "TigerShark" <[email protected]> wrote: Well, as I'm no expert I don't know either, but I thought the dialect implementation had something to do with the way the different db's handled order by's. But after some research I can see that theres nothing about orders in the dialect base class, so I guess it's a sql standard. However, in the links I provided, I read that "nulls first" was sql-99? On 10 Mar., 18:14, Tuna Toksoz <[email protected]> wrote: > I don't know how would you do that with... > Tuna Toksözhttp://tunatoksoz.comhttp://turkiyealt.nethttp:// twitter.com/tehlike > > Typos included... > On Tue, Mar 10, 2009 at 7:08 PM, TigerShark <[email protected] >wrote: > > > > > Hmm, I see. Is that the only way? I was hoping for the dialect to > > handle it for me...?... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
