SQLite upgrade fails about smf HOT 11 CLOSED

What's the best way to fix it?

🚽

😃

from smf.

👼

from smf.

I am just waking up, sleep typing lol. Have you tried sqlite_escape_string()?

from smf.

I tried with $smcFunc['db_escape_string'] that is the equivalent of sqlite_escape_string but no luck... :(

from smf.

Is this still an issue? I don't have an sqlite install that I can test this with.

from smf.

I didn't do anything to fix it, so...yes I'm pretty sure it's still an issue.

from smf.

Just to get my head around this before I look at it, is the issue the double brackets in the PRAGMA call when executing?

from smf.

Technically the issue is that when installing SQLite creates a wrong name for the index I think, then it requires a some trick to remove it.

The basic fix is probably the one I provided above (even though someone with more SQLite knowledge may give advices), the best fix would be to remove the "broken" indexes and replace them with proper names...or something like that.

from smf.

I don't think there's much we can do about the "autoindex" indexes, as they're automatically generated when the primary key isn't an integer (see http://readlist.com/lists/sqlite.org/sqlite-users/7/37230.html). I don't even know if we can actually remove those either.

from smf.

Unfortunately escape_string uses the underlying c function sqlite3_mprintf with the %q operator I believe.

http://www.sqlite.org/c3ref/mprintf.html is the documentation on the function , it doesn't escape the ( or ) characters so passing it to that function won't rectify the issue. Only way that I can think of is a preg_replace or a strtr .

Hope that is of some use...

from smf.

Closing per #1916

from smf.