Using SQLite

Errata for Using SQLite

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.


Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted
PDF Page 40
2nd paragraph

"mark at least one column from each PRIMARY KEY as NOT NULL." This doesn't make sense to me. Should it be "from each table as NOT NULL?"

Anonymous  Aug 26, 2010 
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version Page 56

While browsing through your excellent book "Using SQLite" ISBN:9781449394592 under the "Save-Points" section I noticed some example sql inserts that specified "values" without parentheses, such as: insert into t values 1; I believe parentheses are required, and http://www.sqlite.org/lang_insert.html seems to agree: insert into t values (1); $ sqlite3 SQLite version 3.7.14 2012-09-03 15:42:36 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> create table t; sqlite> insert into t values 1; Error: near "1": syntax error Keep up the good work! Ryan Flynn

Adam Zaremba  Feb 21, 2013 
PDF Page 65
Figure 5-2

In the result of the INNER JOIN, the 3rd row reads "3 a 3 7.3" but should be "3 a 3 2.3"

Anonymous  Jan 13, 2011 
Printed Page 65
Figure 5.2

In the joined table in Fig 5.2, column D contains the value 7.3. This should be 2.3. Table 5.3 on P67 has the same problem.

Tim Streater  Oct 25, 2011 
Printed Page 65
Paragraph after Fig 5-2.

Author used C and D to denotes numbers of columns. As Fig 5-2 has columns named C and D, this was briefly confusing. I would suggest using x and y rather than C and D.

Tim Streater  Oct 25, 2011 
PDF Page 65
Figure 5.2; note pdf version is page 87 of 528

In figure 5.2, the 4th column, 3rd record (of 4) the value is 7.3. It should be 2.3.

Jim Kay  Jan 12, 2014 
PDF Page 78
1st paragraph

Last sentence reads "... the expressions present in any ORDER BY clause must be exactly match one of the result columns ..." I think either the "be" or the "exactly match" but not both ?

Note from the Author or Editor:
Verified in DocBook XML. In paragraph id="ch05_id2303932" the phrase "...the expressions present in any ORDER BY clause must be exactly match one of the result columns..." should be changed to "...the expressions present in any ORDER BY clause must exactly match one of the result columns..." Keeping this as "needs review" because there are other issues with this paragraph I want to think about.

spiceisland  Sep 15, 2010 
PDF Page 120
Last line

The "(SQLITE_READWRITE | SQLITE_CREATE)." in the last line should be changed to "(SQLITE_OPEN_READWRITE | SQLITE_OPEN_CREATE).".

Anonymous  Sep 23, 2010 
Printed Page 471
Definition section of sqlite_rollback_hook()

Provided description of function is: void sqlite3_rollback_hook( sqlite3*db, rollback_callback, void* udp ); void commit_callback( void* udp ); Should the "commit_callback" name really be "rollback_callback", as referenced in the "sqlite3_rollback_hook" definition?

Dennis Amundson  Jan 12, 2013 
ePub Page 1313
Start of description...

“group_concat() — Concatenate row values ... The group_contact() aggregate returns a text value that is the concatenated text representations of each non-NULL element , separated by separator .” Excerpt From: Jay A. Kreibich. “Using SQLite.” O’Reilly Media, 2010-08-10. iBooks. This material may be protected by copyright. group_contact => group_concat

Paul Adams  Mar 09, 2015