No problem (remember that mails are a really bad way to know persons and for something people call me "Brutus"). The correct way to write the HQL is writing what you need in the moment you need it. If you want write always multi-RDBMS HQL you should ensure to use multi-RDBMS functions and, where you need something special, you should extend each dialect properly.
2009/6/3 Dmitiry Nagirnyak <[email protected]> > You don't know the underling DB ? and how you are configuring NH ? >> > Fabio, I'm not talking about configuration but rather writing HQL. > The aim is to *use* HQL without knowledge of the underlying database. (it > is supposed to be persistence ignorant, right?). > This will allow to support other databases supported by NH without > rewriting the actual code. > > >> When you need an extension method what you do ? >> Are you asking to Microsoft to include it in the next .NET version ? >> > Come on... Yes, I'm new to NH and that's why I'm asking obvious questions > (for you). > But there's nothing to do with it. I'm not asking to include a function > into NH. I'm asking about the correct way of writing HQL so I can easily > change database later or support multiple ones. > > Anyway, I'm sorry if I don't understand some things straight away. > > Cheers, > Dmitriy. > > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
