Closed GoogleCodeExporter closed 9 years ago
Moreover, we should get rid of the 2nd "ERROR".
Original comment by crazy4ch...@gmail.com
on 21 Mar 2013 at 11:16
The same problem is likely to happen with any other table-constraint like
CONSTRAINT, CHECK, FOREIGN KEY, PRIMARY KEY, UNIQUE.
See https://www.sqlite.org/syntaxdiagrams.html#table-constraint
We probably need to add some lookahead in $preg_column_definiton that makes
sure no column definition starts with one of these keywords.
Original comment by crazy4ch...@gmail.com
on 21 Mar 2013 at 11:32
The Debug output
Original comment by crazy4ch...@gmail.com
on 22 Mar 2013 at 11:12
Attachments:
Note: This issue only affects SQLite v2 DBs because v3 supports ALTER TABLE ADD
and therefore, our own alterTable() function is not used in this case.
I am currently debugging this. A negative lookahead in $preg_pattern_add and
catching table-constraints behind will do the job.
Original comment by crazy4ch...@gmail.com
on 22 Mar 2013 at 12:44
This issue was closed by revision r379.
Original comment by crazy4ch...@gmail.com
on 22 Mar 2013 at 3:57
I just fixed this using a negative lookahead. Should work for all
table-constraints.
I think we can include this in 1.9.4.1
Original comment by crazy4ch...@gmail.com
on 22 Mar 2013 at 3:59
Original issue reported on code.google.com by
crazy4ch...@gmail.com
on 21 Mar 2013 at 11:14Attachments: