aboutsummaryrefslogtreecommitdiff
path: root/src/random.c
diff options
context:
space:
mode:
authordrh <drh@noemail.net>2002-02-19 13:39:21 +0000
committerdrh <drh@noemail.net>2002-02-19 13:39:21 +0000
commitaaab5725dba68b9c40288cdce11619d601b460c1 (patch)
tree6c86629d0d3df2720d50a732cab4bfcc67c6059c /src/random.c
parenta80a1e6ae42f71331400db08120a8c8646a2f8e9 (diff)
downloadsqlite-aaab5725dba68b9c40288cdce11619d601b460c1.tar.gz
sqlite-aaab5725dba68b9c40288cdce11619d601b460c1.zip
Change the name of the sanity_check PRAGMA to "integrity_check" and make
it available on all compiles. (CVS 381) FossilOrigin-Name: c6e9048e66c8d8e2d5f6c62aa724eef3e9d9f572
Diffstat (limited to 'src/random.c')
-rw-r--r--src/random.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/random.c b/src/random.c
index 2f669ae03..39148b490 100644
--- a/src/random.c
+++ b/src/random.c
@@ -15,7 +15,7 @@
** Random numbers are used by some of the database backends in order
** to generate random integer keys for tables or random filenames.
**
-** $Id: random.c,v 1.9 2002/01/16 21:00:27 drh Exp $
+** $Id: random.c,v 1.10 2002/02/19 13:39:23 drh Exp $
*/
#include "sqliteInt.h"
#include "os.h"
@@ -31,7 +31,7 @@
** well be good enough. But maybe not. Or maybe lrand48() has some
** subtle problems on some systems that could cause problems. It is hard
** to know. To minimize the risk of problems due to bad lrand48()
-** implementations, SQLite uses is this random number generator based
+** implementations, SQLite uses this random number generator based
** on RC4, which we know works very well.
*/
static int randomByte(){