Re: [SQL-Ledger-users] LARGE INVENTORY

[Thomas S. <ps...@on...>]

Dieter,

I don't see how adding a character limit will help both sides in this.
How would you implement this? If you add a character limit then how does
someone pull up a full listing?

Honestly, I think the paging idea was right-on. And that should be the
direction to move in. I didn't realize it at first, but it would not
be that hard.

Here, follow this link and see http://www.oreillynet.com/lpt/a/448.

It is as simple as putting a LIMIT clause in the sql statement. Whether
its a fixed or variable limit is a matter of whether you want to put
a field on the search page for it or not. (Where 0 or blank could mean
all.) 

Yet I would like to point out that the poeple who say they don't want
a limit so they can pull up all their inventory are exactly the ones
who do not have a large inventory to pull up! That's why I think simply
putting a fixed limit of 1,000 for now would be a good compromise, without
much fuss.

-- 
Thomas Sawyer
ps...@on... - email

---- Dieter Simader <dsi...@sq...> wrote:
> 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
> =========== On a clear disk you can seek forever ===========
> 
> On Tue, 6 Feb 2001, Matt Benjamin wrote:
> 
> > 
> > I like this suggestion.  It would allow you to browse all available
> data
> > in user-configurable increments.
> > 
> > It is also a very familiar interface on the web, which would make
> it easy
> > 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.)
> > 
> > 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, [iso-8859-1] Claudio Santana 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ó: > 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ón 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