I found another resolution for my problem.
If I create an index for orderbyed column, my problem will get gone.
After reading some docs about sqlite, it seems that using index to
order by will remove the necessary of creating journal file.
So I think creating index is a better solution.
--
After digging further, I got it.
This disk I/O error is caused because the default size(4m) of
sqlite_stmt_journals partition is too small for our query.
If I changed init.rc to make big size partition(8m), 4000 rows data
can be selected without any error.
So I wonder what is the best solution
If I were to design such an app, I would only pull the data I needed
at that moment. Are you going to use 4000 rows of data in one swoop or
are you using a subset of that query? Most likely, your app is going
to have a next/previous type setup. Sucking up 4000 rows from the
database will not only
3 matches
Mail list logo
