Re: [SQL-Ledger-users] LARGE INVENTORY

[Matt B. <ma...@li...>]

Being able to scroll through long listings, possibly with a configurable
page size, seems like an (eventual) requirement.  I do not see the value
in getting just the top 1000 (or however many) entries.


Matt


Matt Benjamin President/CTO

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

tel. 734-761-4689
fax. 734-769-8938
pgr. 734-431-0118

On Tue, 6 Feb 2001, Thomas Sawyer wrote:

> I thought about that. In fact I was looking at Border's book search site
> and they have a neat way of doing this by having links for each set at
> the top of the page i.e. 1-50 | 51-100 | 101-150 ...etc. But its not
> such a great idea I think b/c if you do a serach and your item ends up
> on the 2nd or 3rd or 4th... page then you have to go through multiple
> links (and hence waitings) to find it. Its much easier to scroll down
> to find something and sql-ledger can load a 1,000 items pretty fast.
>
> --
> Thomas Sawyer
> ps...@on... - email
> (303) 285-3487 x1594 - voicemail/fax
>
>
>
> ---- =3D?iso-8859-1?q?Claudio=3D20Santana?=3D <tra...@ya...> wrote=
:
> >    I think it would be better to slice this huge page in pages of n
> > elements and then display just n elements and give to the user a next
> > page link or button so we will just be selecting from the DB all the
> > elements but the heavy operation that is generating the page will be
> > done with a subset of all the elements. But in this case we should
> > keep the state of the module, I mean the "next page" will mean
> > different places every time we show it. So we could put that
> > information in the "next page" link, we could include the query
> > parameters and the next starting ID for the next page, and the same
> > for "prev page" . Do I explain my self?
> >
> > Claudio Santana.
> >
> > --- Martin Lillepuu <ma...@li...> escribi=F3: > Thomas Sawyer
> > wrote:
> > >
> > > > I have to get this working with this a large inventory. So I'm
> > > looking
> > > > at adding some selection criteria limitations to the ic.cgi
> > > script. I'm
> > > > thinking of adding limiting criteria where one has to select the
> > > first
> > > > and second letter of the search. (i.e. Aa, Ab, Ac...Zx, Zy, Zz)
> > > How does
> > > > this sound to you all? Any other ideas?
> > >
> > > maybe you should create a new parameter (eq. min_search_str_length)
> > > in
> > > configuration page, so people with small inventories (like me) can
> > > set
> > > it to 0 and in your case, it can be set to 2, 3 or whatever. then
> > > add
> > > code to ic.cgi that displays error message if search string is
> > > shorter
> > > than value specified in config. does this make any sense or am I
> > > over-complicating things again? :)
> > >
> > > another idea to consider is grouping inventory items, so that you
> > > first
> > > select group and then only products belonging to specified group
> > > are
> > > displayed.
> > >
> > > idea #3 - limit displaying inventory items on one page (does
> > > PostgreSQL
> > > have equivalent to MySQL LIMIT?). Maybe implement this throughout
> > > the
> > > program + another option to config page?
> > >
> > > --
> > > Martin Lillepuu | E-mail: ma...@li... | GSM: 051 56 450
> > >
> >
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Obtenga su direcci=F3n de correo-e gratis @yahoo.com
> > en http://correo.espanol.yahoo.com
> >
> >
>
> __________________________________________________
> FREE voicemail, email, and fax...all in one place.
> Sign Up Now! http://www.onebox.com
>
>