Re: [SQL-Ledger-users] LARGE INVENTORY

[Dieter S. <dsi...@sq...>]

Slicing output into pages does not work very well.

I'll add an option to limit searches by forcing users to enter a minimum
number of characters for those who can't teach their users to enter
something. This leaves the program the way it is for people who like to
produce a complete inventory listing and limits output for those who need
a limit.

It used to be in version 0.1, I'll add it again for version 1.4


Dieter Simader    http://www.sql-ledger.org   (780) 472-8161
DWS Systems Inc.     Accounting Software       Fax: 478-5281
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D On a clear disk you can seek forever =3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

On Tue, 6 Feb 2001, Matt Benjamin wrote:

>=20
> I like this suggestion.  It would allow you to browse all available dat=
a
> in user-configurable increments.
>=20
> It is also a very familiar interface on the web, which would make it ea=
sy
> and comfortable for end-users to learn.  (Reading "Phillip and Alex's
> Guide to Web Publishing" has opened my eyes to the importance of
> easy-to-learn interfaces, I think.)
>=20
> Matt
>=20
>=20
> Matt Benjamin President/CTO
>=20
> The Linux Box
> 206 South Fifth Ave. Suite 150
> Ann Arbor, MI  48104
>=20
> tel. 734-761-4689
> fax. 734-769-8938
> pgr. 734-431-0118
>=20
> On Tue, 6 Feb 2001, [iso-8859-1] Claudio Santana wrote:
>=20
> >    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
> >
>=20
>=20
>=20