android - SQLiteQueryBuilder vs Simple String -


i trying make app fast , reactive possible. wonder better, using simple string object or use sqlitequerybuilder.

i'm not 100% sure mean "simple string object" spoken, can quite sure in-memory operation strings faster database operations.

however, not indicator sqlite being bad database (regarding performance), rather result of robust system persists data file system, offers acid transactions , supports sql92 standard (just mention features). if don't need these features , if want maximum performance: store in "simple string objects".

if want take advantage of database features above, might consider using sqlite in-memory database. see sqliteopenhelper() more details.

looking @ sqlite advised dig prepared statements, transaction contexts , indices best performance (see instance articles #1 , #2).

good luck!


Comments

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

jsf - How to ajax update an item in the footer of a PrimeFaces dataTable? -

django - CSRF verification failed. Request aborted. CSRF cookie not set -