Re: [SQL-Ledger-users] LARGE INVENTORY

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

I see! You mean to offer both -- a user definable # or records returned,
but per page, and then links to the other pages (ie. back, next, 1-50,
51-100, etc.) Perfect!

So who wants to do it?

Also, Dieter Simader, where does version 1.4 stand? Is it close to realease?
How will our changes be effective with that new version? Do we just tell
you about them and you'll see about putting them in? Guess I'm a little
confused about the how's of this collabrotive open-source development
thing. I looked on ScourceForge and all I saw was the 1.2.5 release,
not even the current 1.2.7. Right now I'm becoming a SourceForge member.
I'm thinking, this might make a difference and I'd be able to find the
lastest in-development version (1.4). Is CVS being used here?


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

---- Matt Benjamin <ma...@li...> 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