harryh writes:
>> http://github.com/dpp/liftweb/commit/58c5463d44948a48dd2fa62bf9d14960...
>
> Any idea how long it will be until this is in a non snapshot build? I
> guess I just missed the M5 release. I'm a little scared of pushing
> production code based on 1.1-SNAPSHOT. Anyone out there do
On Thu, Sep 10, 2009 at 1:07 PM, harryh wrote:
>
> > http://github.com/dpp/liftweb/commit/58c5463d44948a48dd2fa62bf9d14960...
>
> Any idea how long it will be until this is in a non snapshot build? I
> guess I just missed the M5 release. I'm a little scared of pushing
> production code based on
> http://github.com/dpp/liftweb/commit/58c5463d44948a48dd2fa62bf9d14960...
Any idea how long it will be until this is in a non snapshot build? I
guess I just missed the M5 release. I'm a little scared of pushing
production code based on 1.1-SNAPSHOT. Anyone out there doing this
sort of thing?
On Thu, Sep 10, 2009 at 12:02 PM, harryh wrote:
>
> > A fix is in the works.
>
> Awesome. Thanks!!!
>
http://github.com/dpp/liftweb/commit/58c5463d44948a48dd2fa62bf9d14960d2eaf6d4
>
> -harryh
> >
>
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.a
> A fix is in the works.
Awesome. Thanks!!!
-harryh
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send e
On Thu, Sep 10, 2009 at 11:32 AM, harryh wrote:
>
> ~1125 ms for your query.
> ~50ms for the IN based on that lift currently generates.
>
> This is doing things in the psql console on the same machine the
> database lives on. It's not so much the query time that concerns me,
> as the amount of d
On Thu, Sep 10, 2009 at 8:32 PM, harryh wrote:
>
> ~1125 ms for your query.
> ~50ms for the IN based on that lift currently generates.
>
*laughs* Query optimizers in the different RDBMSes never cease to amaze me
;D
Just for kicks, what about this?
SELECT DISTINCT users.id, users.firstname, us
~1125 ms for your query.
~50ms for the IN based on that lift currently generates.
This is doing things in the psql console on the same machine the
database lives on. It's not so much the query time that concerns me,
as the amount of data being sent back in the results. In my example
at the top
On Thu, Sep 10, 2009 at 8:15 PM, Viktor Klang wrote:
>
>
> On Thu, Sep 10, 2009 at 6:23 PM, harryh wrote:
>
>>
>> Consider:
>>
>> val venues = Venue.findAll(By(Venue.cityid, City.currentCity),
>> NotNullRef(Venue.owner),
>> OrderBy(Venue
On Thu, Sep 10, 2009 at 6:23 PM, harryh wrote:
>
> Consider:
>
> val venues = Venue.findAll(By(Venue.cityid, City.currentCity),
> NotNullRef(Venue.owner),
> OrderBy(Venue.id, Descending),
> MaxRows(10),
>
10 matches
Mail list logo