我正在努力提高我的android数据库插入速度。我目前正在做的是生成一个字符串,如:
SELECT ? as title, ? as musician_id, ? as album_id, ? as genre
UNION SELECT ?, ?, ?, ?
UNION SELECT ?, ?, ?, ?
UNION SELECT ?, ?, ?, ?
UNION SELECT ?, ?, ?, ?
UNION SELECT ?, ?, ?, ?
然后用
执行它SQLiteDatabase database = //initialized in some way
String insertQuery; // the string of the query above
String [] parameters; // the parameters to use in the insertion.
database.execSQL(insertQuery.toString(), parameters);
当我尝试插入大约2000行时,我收到以下错误:
Caused by: android.database.sqlite.SQLiteException: too many SQL variables (code 1): , while compiling: INSERT INTO songs (title, musician_id, album_id, genre)
SELECT ? as title, ? as musician_id, ? as album_id, ? as genre
UNION SELECT ?, ?, ?, ?
UNION SELECT ?, ?, ?, ?
当我尝试插入大约200行时,一切正常。
我想这很明显 - 我试图在一个execSQL
中传递太多变量。有谁知道限制是什么,以便我可以分割我在适当批次中插入的行?
答案 0 :(得分:25)
限制在sqlite3.c中被硬编码并设置为999.不幸的是,它只能在编译时更改。以下是相关摘要:
/*
** The maximum value of a ?nnn wildcard that the parser will accept.
*/
#ifndef SQLITE_MAX_VARIABLE_NUMBER
# define SQLITE_MAX_VARIABLE_NUMBER 999
#endif
/*
** The datatype ynVar is a signed integer, either 16-bit or 32-bit.
** Usually it is 16-bits. But if SQLITE_MAX_VARIABLE_NUMBER is greater
** than 32767 we have to make it 32-bit. 16-bit is preferred because
** it uses less memory in the Expr object, which is a big memory user
** in systems with lots of prepared statements. And few applications
** need more than about 10 or 20 variables. But some extreme users want
** to have prepared statements with over 32767 variables, and for them
** the option is available (at compile-time).
*/
#if SQLITE_MAX_VARIABLE_NUMBER<=32767
typedef i16 ynVar;
#else
typedef int ynVar;
#endif
答案 1 :(得分:14)
我正在尝试提高我的Android数据库插入速度。什么 我目前正在做的是生成一个字符串,如:
您是否考虑过使用 TRANSACTION
?我建议你用它代替你的方法。我认为使用 UNION
条款根本不是“胜利”,并且有更好,更主要的方法来实现它。
db.beginTransaction();
try {
for (int i = 0 ; i < length ; i++ ) { // or another kind of loop etc.
// make insert actions
}
db.setTransactionSuccessful(); // now commit changes
}
finally {
db.endTransaction();
}