Drake, hello. On 2010 Dec 26, at 18:26, Drake Wilson wrote:
> Quoth Norman Gray <nor...@astro.gla.ac.uk>, on 2010-12-26 18:14:23 +0000: >> The phrase "For each UNIQUE constraint on the table" appears to be >> redundant; if it's not, then that might need to be adjusted. > > A UNIQUE specifier on a column creates one UNIQUE constraint on > exactly that column. UNIQUE specifiers on multiple columns are > unrelated. You may specify a multi-column UNIQUE constraint by > declaring it separately (and not as part of any column specification). Thanks for that. That's what I eventually worked out (as I noted). I don't think that's reasonably deducible from the passage I quoted, however, so this is a documentation bug rather than an implementation bug. (The documentation is clear, once you know the answer, but ...) Simply adding: >> A UNIQUE specifier on a column creates one UNIQUE constraint on >> exactly that column. UNIQUE specifiers on multiple columns are >> unrelated. ...to the documentation would make this clearer. It appears that column UNIQUE constraints are not discussed on that page. Best wishes, Norman -- Norman Gray : http://nxg.me.uk Dept Physics and Astronomy, University of Glasgow, UK _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
