>Ah, there is a way to write it so that you can have at most one of >those constraints where only one makes sense, and not require a >specific order of constraints, but it'd require listing all the >possible orderings, which would be impractical. > >So if one wanted to enforce that there's at most one of such >constraints then the best pace to do it in in sqlite3AddDefaultValue() >and friends, rather than in the grammar. But really, is it worth it?
No, certainly not. SQLite parser is fine like it is, no reason to bloat it with much fat just to flag ill constructs, particularily in this cas where there's no harm done. Thanks Nico for looking and for your detailed explanation. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
