On Aug 13, 2008, at 10:59 AM, Dennis Cote wrote: > D. Richard Hipp wrote: >> >> (2) Formal and detail requirements that define precisely what SQLite >> does. >> >> http://www.sqlite.org/draft/tokenreq.html >> http://www.sqlite.org/draft/syntax.html >> > > These look great. I noticed a few typos, but on the whole they are > very > good. > > I noticed that in many places you specify that sqlite will fail with > an > error, but you do not specify what the error will be (i.e. the error > code and or message isn't specified). Perhaps these details should > be added.
Consider what happens if an interaction with the library contains two or more errors. Only a single error message and error code can be returned. Consequently, if the interaction contains error A we cannot guarantee that the code and message returned will refer to A, since it might instead refer to error B. We can guarantee that some kind of error will be returned. We just cannot guarantee what the error code and message content will be since that depends on what other errors might be present. D. Richard Hipp [EMAIL PROTECTED] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
