Re: [Webware-discuss] Algorithm to handle big data selections

2002-12-26 Thread Michael Engelhart
Thanks for bringing that up. I do use an ORDER BY but for some reason forgot to mention it. mike On Thursday, December 26, 2002, at 12:42 PM, Tim Roberts wrote: If you will allow me to slide into SQL pedantics for a moment, you should always use an ORDER BY clause when using LIMIT and OFFSET

Re: [Webware-discuss] Algorithm to handle big data selections

2002-12-26 Thread Tim Roberts
On Tue, 24 Dec 2002 10:00:46 +0100, Frank Barknecht <[EMAIL PROTECTED]> wrote: > >Hi, >Michael Engelhart hat gesagt: // Michael Engelhart wrote: > >> I use PostgreSQL and you can do something like: >> >> SELECT * FROM my_table LIMIT 25 OFFSET 25 >> >> which would return 25 rows starting with the

Re: [Webware-discuss] Algorithm to handle big data selections

2002-12-24 Thread Frank Barknecht
Hi, Michael Engelhart hat gesagt: // Michael Engelhart wrote: > I use PostgreSQL and you can do something like: > > SELECT * FROM my_table LIMIT 25 OFFSET 25 > > which would return 25 rows starting with the 25th row in the result set. > > mySQL has something similar I believe which is something

Re: [Webware-discuss] Algorithm to handle big data selections

2002-12-23 Thread Aaron Held
> I went another route in my prototype and I'd like to hear some > comments: > No shortage of opinions here! > I have a class "Product" that represents a Product: > >> start py code > class Product: >def __init__(self, id): >db = datapool.getConnection() >

Re: [Webware-discuss] Algorithm to handle big data selections

2002-12-23 Thread Michael Engelhart
I would tend to let the database handle as much of this as possible. There are many SQL additions that can help here. I use PostgreSQL and you can do something like: SELECT * FROM my_table LIMIT 25 OFFSET 25 which would return 25 rows starting with the 25th row in the result set. mySQL has s

Re: [Webware-discuss] Algorithm to handle big data selections

2002-12-23 Thread Frank Barknecht
Hi, Aaron Held hat gesagt: // Aaron Held wrote: > I built a extranet application that pulled up to 5000 records (up to 30 > * 50char text fields and a few dates) > This was generated by a long SQL query that could take up to 12 seconds > and here was my plan: > [...] Wow, this looks like heavy w

Re: [Webware-discuss] Algorithm to handle big data selections

2002-12-23 Thread Aaron Held
I built a extranet application that pulled up to 5000 records (up to 30 * 50char text fields and a few dates) This was generated by a long SQL query that could take up to 12 seconds and here was my plan: 1) spawn a extra thread to pull the sql 2) when the sql was done update a flag in the users

[Webware-discuss] Algorithm to handle big data selections

2002-12-23 Thread Max Ischenko
Hi. I have a servlet which prompts user for some values, then search the database using entered keys and the display the result back to the user. I want to break results into pieces so it would load more quickly and reduce server loading (generating HTML from 3000 records take quite a few time).