Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <69a992ac0906201915p5d3073l8af5812ed411d76d@mail.gmail.com>
References: <69a992ac0906191748q160ac0fct5c26c408da593bbf@mail.gmail.com>
	 <e2111bbb0906191751i3e56814dl9a0d1479ae10846c@mail.gmail.com>
	 <69a992ac0906191802l160d5937qf4b723bffd8c9928@mail.gmail.com>
	 <e2111bbb0906201242x5cd4a46dhf88eb09c3a3aef21@mail.gmail.com>
	 <69a992ac0906201915p5d3073l8af5812ed411d76d@mail.gmail.com>
Date: Mon, 22 Jun 2009 13:01:28 +1000
Message-ID: <55047b710906212001i2a0aa70clb6e0d974f47be9fc@mail.gmail.com>
Subject: Re: view sorting and group question?
From: Nicholas Orr <nicholas.orr@zxgen.net>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=000e0cd2e12c285140046ce71745

--000e0cd2e12c285140046ce71745
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

You could use another tool like ExtJS on the client side to filter and sort
results.
I'm using the Ext.grid.GridPanel with a Ext.ux.data.JsonPagingStore.

However there are things to consider with this particular approach.
The JsonPagingStore retrieves the whole set of data returned from the
view and stores it client side to filter
& sort.
Using start_key & end_key doesn't apply so if your data grows to be like
2000 records, 2000 records will be loaded by the grid :)

I won't reach 30 records with what I'm doing so it's fine to have 30 records
coming down the wire to the client.

Plus other thing to consider with this approach is it means learning ExtJS
which isn't exactly simple, take a bit of effort ;)

Nick

On Sun, Jun 21, 2009 at 12:15 PM, hhsuper <hhsuper@gmail.com> wrote:

> but if i need to use the view as a datasource to the web page, i need
> change
> to right view to query on every sorting?
>
> On Sun, Jun 21, 2009 at 3:42 AM, Paul Davis <paul.joseph.davis@gmail.com
> >wrote:
>
> > On Fri, Jun 19, 2009 at 9:02 PM, hhsuper<hhsuper@gmail.com> wrote:
> > > thanks paul,
> > >
> > > do you mean i need another view to resolve this, the difference between
> > them
> > > are the key order?
> > >
> >
> > Yeah, if you're wanting to 'resort' a view, the CouchDB way is to
> > create a second view for each 'sort order'.
> >
> > HTH,
> > Paul Davis
> >
> > > i mean i want to group or sort not with start at the first key, could i
> > > achieve this goal in only view?
> > >
> > > On Sat, Jun 20, 2009 at 8:51 AM, Paul Davis <
> paul.joseph.davis@gmail.com
> > >wrote:
> > >
> > >> If you want different key sorting then you'll need to emit different
> > >> keys. The same goes for grouping differently.
> > >>
> > >> Paul Davis
> > >>
> > >> On Fri, Jun 19, 2009 at 8:48 PM, hhsuper<hhsuper@gmail.com> wrote:
> > >> > Hi, my view return structure like this:
> > >> >
> > >> >
> > >>
> >
> "key":["1","10075","351"],"value":{"count":27420,"score":2085790,"grade":76.06819839533188}
> > >> >
> > >> >
> > >> > the key column refer to userid, dialogid and seesionid, i know i can
> > >> group
> > >> > with userid or with userid, dialogid, but how can i group with
> > >> > dialogid or dialogid,
> > >> > sessionid?
> > >> > also about the sorting, the default is using all key, how can i
> > sorting
> > >> only
> > >> > with userid or only with dialogid?
> > >> >
> > >> > give some suggestion pls.
> > >> >
> > >> > --
> > >> > Yours sincerely
> > >> >
> > >> > Jack Su
> > >> >
> > >>
> > >
> > >
> > >
> > > --
> > > Yours sincerely
> > >
> > > Jack Su
> > >
> >
>
>
>
> --
> Yours sincerely
>
> Jack Su
>

--000e0cd2e12c285140046ce71745--