On 4/19/19, Luuk <[email protected]> wrote: > > On 19-4-2019 16:19, Semih Hazar wrote: >> Hi, >> >> With 3.28.0 I'm getting an inconsistent behavior if I try to rename a >> table >> if its name starts with "sqlite". It's not "sqlite3_" by the way, which >> just gives an error since it's a reserved keyword. >> > > This is the same behavior as in 3.27.2: >
The bug was introduced in version 3.25.0. It was due to a LIKE pattern attempting to match against "sqlite_%%" except "_" means "match any single character to to LIKE operator, so we had to go back in and escape that character. The problem is fixed on trunk. You can find the relevant changes and a reference to the ticket on the timeline: https://www.sqlite.org/src/timeline?ymd=20190419 -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
