Quoth Norman Gray <nor...@astro.gla.ac.uk>, on 2010-12-26 22:02:39 +0000: > Aha: this is a key point. In order to successfully parse the > paragraph, the reader has to be aware that a column constraint and a > table constraint are importantly different things, even though they > look very similar to each other, to someone not steeped in SQL.
I think this is part of the disconnect. I don't get the feeling that the SQLite documentation is intended for people who have little or no SQL background, but rather as a reference for those who are already familiar with SQL relational databases, but not SQLite particularly. So while the full syntax and semantics are provided so that one doesn't have to constantly cross-reference standards documents or such and so that important variations in the language handling can be called out more easily, I'd rather the manual not try to emphasize common elements such as the distinction between column and table constraint syntax. A general SQL tutorial or quick reference should be used for that. Note that the two paragraphs quoted refer to both the column and table forms of UNIQUE and PRIMARY KEY, and they are isomorphic to each other in that each has both forms, so the second paragraph implies repeating both pieces of information from the first. So there is no "different thought in between" exactly. Obviously this is easier for someone who already understands the base syntax well enough, but see above, &c. ---> Drake Wilson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
