Hi Oskar, I tried to keep it simple as in most cases, aggregations are not needed in my design. These aggregations are needed for reporting purposes so could be worked around with stored procs is there is no other option.
You make a fair point about different currency values but in this scenario they are all the same currency and, if it isn't then that's my problem to sort out the corrupt results not NH. Ok, if it's not built in to NH, and I don't have the understanding to code an extension myself. Is there any way I can intercept the query being generated and apply some custom logic to only pass the decimal part of the money to the server? A custom dialect perhaps? -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
