Hello again !
Although this problem is now fixed on trunk maybe would be a good idea to
issue warnings to prevent new code to use this flaws ?
Maybe sqlite3 executable could emit warnings to stderr when it finds bad
usage on a database for the problems that we already know, like this one ?
?
Example:
sqlite3 a_db_that_uses_malformed_sql.db
-- warning
-- use of single quotes on field names are not standard
-- the_index_table_has_the_problem
sqlite3>
?
Cheers !
?
> Fri Sep 04 2015 11:40:11 am CEST CEST from "Domingo Alvarez Duarte"
><sqlite-mail at dev.dadbiz.es> Subject: [sqlite] Changes to create index on
>trunk is breaking old code
>
> Hello !
>
> I'm testing sqlite3 trunk on existing code and noticed that the changes to
> "create index" using expressions/functions is breaking on old databases
>
> It seems that because I used the field name single quotes now it's
> considering it an expression.
>
> On an old database I have the following to create an index:
>
> CREATE INDEX companies_number_idx ON companies ('number');
>
> ?
>
> Now if I try to do anything on that database with sqlite3 trunk I get this
> error message:
>
> malformed database schema (companies_number_idx) - indexes on expressions
>not
> yet supported
>
> ?
> _______________________________________________
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
>
>
?
