Fix the CREATE TABLE performance issue described by
[forum:/forumpost/
4cf69794d9dfff7c|forum thread
4cf69794d9dfff7c] in two
different ways: (1) Omit the call to PRAGMA integrity_check('X') that was
being done after CREATE TABLE "X" because the result was being ignored and
the integrity_check was not doing anything other than burning CPU cycles.
(2) Do not interpret the argument to PRAGMA integrity_check as a number if it
is in fact a string that looks like a number.
FossilOrigin-Name:
71f08b912251c8a3ac1bd8e344903336648e4187f7493f8c126e60b3b51b9f09