The issue is fixed in 2.0-M2 and 2.0-SNAPSHOT On Thu, Feb 18, 2010 at 12:30 PM, Petr Pudlak <[email protected]> wrote:
> Hi, > > I'm having problems with unnecessary SELECT DISTINCT produced by Lift > Mapper. I know that it has been discussed before, but still it causes > problems. Even when I'm doing simple queries into just a single table, > Lift Mapper almost always adds the DISTINCT keyword. Unfortunately, > this has a large negative impact on the performance of my database > (Postgre, to be specific). > Is there a way how to manually disable adding the DISTINCT keyword? > For example, is there a query modifier (something like MaxRows(...)) > which will force Lift Mapper to use plain SELECT without DISTINCT? > Otherwise it looks like I'll have to manually rewrite all queries :-(. > We're having a lots of data and we can't afford such a huge > performance impact. > > Thanks for help. > Petr > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<liftweb%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=en. > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics -- You received this message because you are subscribed to the Google Groups "Lift" 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/liftweb?hl=en.
