I have tested up to 300k rows without a problem so i doubt its with the
sqlite side of things. However setting a dataprovider on a chart of grid
with 40k rows is bound to give you problems.
you can also use offset and limit in sqlite to page
for example
select * from table limit 100 offset 400;
thus start at row 400 and get 100.
On Sat, Jul 12, 2008 at 8:09 PM, George <[EMAIL PROTECTED]> wrote:
> Whatever you should retrieve data in parts if too much rows.
>
> var stmt:SQLStatement = new SQLStatement();
> stmt.sqlConnection = conn;
> stmt.text = "SELECT ...";
> stmt.addEventListener(SQLEvent.RESULT, selectResult);
> stmt.execute(20); // only the first 20 rows (or fewer) are returned
>
> function selectResult(event:SQLEvent):void
> { var result:SQLResult = stmt.getResult();
> if (result.data != null) { // ... loop through the rows or perform other
> processing ...
> if (!result.complete) {
> stmt.next(20); // retrieve the next 20 rows
> } else { stmt.removeEventListener(SQLEvent.RESULT, selectResult);
>
> } } }
>
> Josh Millstein wrote:
> >
> > Hello,
> >
> > My AIR app is crashing on a sql statement (I think) that is returning
> > around
> > 40000 rows. Should that be happening? Is there a max execution time for
> > sql queries that could be crashing adl? Is there anything I can do to fix
> > this problem, if the execution time or the number rows returned is a
> > problem?
> >
> > Thanks,
> > Josh
> > --
> > [EMAIL PROTECTED] <wolf%40wolffebrothers.com> <mailto:
> wolf%40wolffebrothers.com <wolf%2540wolffebrothers.com>>
> > 785-832-9154
> >
> > __.
>
>
>
--
j:pn
\\no comment
