Hi Ben,
I don't think it is the list widget that is the problem. I think it just takes Rev a long time to retrieve a large amount of data from an SQL database, especially if it is a remote database. I have made the same mistake and set it to get all the data from a table with about 25000 records and it took about a minute, but the data was being assembled in RAM and only put into the list field at the very end of the script. With Rev 2.5, I have never had it fail completely, just take a while.
Cheers, Sarah
On 11 Oct 2004, at 12:13 pm, VHD wrote:
I have been doing some experiments with displaying information from a database into the list widget.
It looks like it does not handle large amounts of rows very well.
It starts struggling when displaying more than 500 rows with 5 columns.
Even though this is not a huge problem since one would not want so many rows anyway, it does make me wonder how well the list widget is implemented.
The only reason I found this out was using Sarah Reichelt's MySQLtest stack. I inadvertently selected a table that had 20 thousand rows and it took for ever (i.e. after a few minutes I had to "kill" revolution and start it up again.)
That is when I started experimenting by placing a LIMIT on the sql statements. I found that things started slowing down after 500 rows.
Does anyone know if a better list widget is in the works? (or perhaps I might be doing something wrong...)
Thanks,
Ben
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
