Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | :-) (CVS 2) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
53841c66c699665e83c933627bbe7a19 |
User & Date: | drh 2000-05-29 17:44:25.000 |
Context
2000-05-29
| ||
18:20 | :-) (CVS 3) (check-in: 9e36a6014b user: drh tags: trunk) | |
17:44 | :-) (CVS 2) (check-in: 53841c66c6 user: drh tags: trunk) | |
14:26 | initial check-in of the new version (CVS 1) (check-in: 6f3655f79f user: drh tags: trunk) | |
Changes
Changes to Makefile.in.
︙ | ︙ | |||
40 41 42 43 44 45 46 | # Object files for the SQLite library. # LIBOBJ = build.o dbbe.o main.o parse.o tokenize.o util.o vdbe.o where.o # This is the default Makefile target. The objects listed here # are what get build when you type just "make" with no arguments. # | | | | 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 | # Object files for the SQLite library. # LIBOBJ = build.o dbbe.o main.o parse.o tokenize.o util.o vdbe.o where.o # This is the default Makefile target. The objects listed here # are what get build when you type just "make" with no arguments. # all: libsqlite.a sqlite.h sqlite # libtclsqlite.a tclsqlite libsqlite.a: $(LIBOBJ) $(AR) libsqlite.a $(LIBOBJ) $(RANLIB) libsqlite.a sqlite: $(TOP)/src/shell.c libsqlite.a sqlite.h $(TCC) $(READLINE_FLAGS) -o sqlite $(TOP)/src/shell.c \ libsqlite.a $(LIBGDBM) $(LIBREADLINE) # Rules to build the LEMON compiler generator # lemon: $(TOP)/tool/lemon.c $(TOP)/tool/lempar.c $(BCC) -o lemon $(TOP)/tool/lemon.c |
︙ | ︙ | |||
83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 | $(TCC) $(GDBM_FLAGS) -c parse.c parse.h: parse.c parse.c: $(TOP)/src/parse.y lemon cp $(TOP)/src/parse.y . ./lemon parse.y tokenize.o: $(TOP)/src/tokenize.c $(HDR) $(TCC) $(GDBM_FLAGS) -c $(TOP)/src/tokenize.c util.o: $(TOP)/src/util.c $(HDR) $(TCC) $(GDBM_FLAGS) -c $(TOP)/src/util.c vdbe.o: $(TOP)/src/vdbe.c $(HDR) $(TCC) $(GDBM_FLAGS) -c $(TOP)/src/vdbe.c where.o: $(TOP)/src/where.c $(HDR) $(TCC) $(GDBM_FLAGS) -c $(TOP)/src/where.c clean: | > > > > > > > > > > > > > > > > > > > > > | | | 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 | $(TCC) $(GDBM_FLAGS) -c parse.c parse.h: parse.c parse.c: $(TOP)/src/parse.y lemon cp $(TOP)/src/parse.y . ./lemon parse.y sqlite.h: $(TOP)/src/sqlite.h cp $(TOP)/src/sqlite.h . tokenize.o: $(TOP)/src/tokenize.c $(HDR) $(TCC) $(GDBM_FLAGS) -c $(TOP)/src/tokenize.c util.o: $(TOP)/src/util.c $(HDR) $(TCC) $(GDBM_FLAGS) -c $(TOP)/src/util.c vdbe.o: $(TOP)/src/vdbe.c $(HDR) $(TCC) $(GDBM_FLAGS) -c $(TOP)/src/vdbe.c where.o: $(TOP)/src/where.c $(HDR) $(TCC) $(GDBM_FLAGS) -c $(TOP)/src/where.c TARBALL = \ sqlite/doc/*.html \ sqlite/src/*.h \ sqlite/src/*.c \ sqlite/tool/*.c \ sqlite/tool/*.awk \ sqlite/configure \ sqlite/*.in sqlite.tar.gz: pwd=`pwd`; cd $(TOP)/..; tar czf $$pwd/sqlite.tar.gz $(TARBALL) index.html: $(TOP)/www/index.tcl sqlite.tar.gz tclsh $(TOP)/www/index.tcl >index.html sqlite.html: $(TOP)/www/sqlite.tcl tclsh $(TOP)/www/sqlite.tcl >sqlite.html clean: rm -f *.o sqlite libsqlite.a sqlite.h rm -f lemon lempar.c parse.* sqlite.tar.gz |
Changes to src/build.c.
︙ | ︙ | |||
20 21 22 23 24 25 26 | ** drh@hwaci.com ** http://www.hwaci.com/drh/ ** ************************************************************************* ** This file contains C code routines that are called by the parser ** when syntax rules are reduced. ** | | | 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 | ** drh@hwaci.com ** http://www.hwaci.com/drh/ ** ************************************************************************* ** This file contains C code routines that are called by the parser ** when syntax rules are reduced. ** ** $Id: build.c,v 1.2 2000/05/29 17:44:25 drh Exp $ */ #include "sqliteInt.h" /* ** This routine is called after a single SQL statement has been ** parsed and we want to execute the code to implement ** the statement. Prior action routines should have already |
︙ | ︙ | |||
239 240 241 242 243 244 245 | ** Add a new column to the table currently being constructed. */ void sqliteAddColumn(Parse *pParse, Token *pName){ Table *p; char **pz; if( (p = pParse->pNewTable)==0 ) return; if( (p->nCol & 0x7)==0 ){ | | | 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 | ** Add a new column to the table currently being constructed. */ void sqliteAddColumn(Parse *pParse, Token *pName){ Table *p; char **pz; if( (p = pParse->pNewTable)==0 ) return; if( (p->nCol & 0x7)==0 ){ p->azCol = sqliteRealloc( p->azCol, (p->nCol+8)*sizeof(p->azCol[0])); } if( p->azCol==0 ){ p->nCol = 0; return; } pz = &p->azCol[p->nCol++]; *pz = 0; |
︙ | ︙ | |||
284 285 286 287 288 289 290 | /* If not initializing, then create the table on disk. */ if( !pParse->initFlag ){ static VdbeOp addTable[] = { { OP_Open, 0, 0, MASTER_NAME }, { OP_New, 0, 0, 0}, { OP_String, 0, 0, "table" }, | | | | | | | | 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 | /* If not initializing, then create the table on disk. */ if( !pParse->initFlag ){ static VdbeOp addTable[] = { { OP_Open, 0, 0, MASTER_NAME }, { OP_New, 0, 0, 0}, { OP_String, 0, 0, "table" }, { OP_String, 0, 0, 0}, /* 3 */ { OP_String, 0, 0, 0}, /* 4 */ { OP_String, 0, 0, 0}, /* 5 */ { OP_MakeRecord, 4, 0, 0}, { OP_Put, 0, 0, 0}, { OP_Close, 0, 0, 0}, }; int n, base; Vdbe *v = pParse->pVdbe; if( v==0 ){ v = pParse->pVdbe = sqliteVdbeCreate(pParse->db->pBe); } if( v==0 ) return; n = (int)pEnd->z - (int)pParse->sFirstToken.z + 1; base = sqliteVdbeAddOpList(v, ArraySize(addTable), addTable); sqliteVdbeChangeP3(v, base+3, p->zName, 0); sqliteVdbeChangeP3(v, base+4, p->zName, 0); sqliteVdbeChangeP3(v, base+5, pParse->sFirstToken.z, n); } } /* ** Given a token, look up a table with that name. If not found, leave ** an error for the parser to find and return NULL. */ |
︙ | ︙ |
Changes to src/shell.c.
︙ | ︙ | |||
20 21 22 23 24 25 26 | ** drh@hwaci.com ** http://www.hwaci.com/drh/ ** ************************************************************************* ** This file contains code to implement the "sqlite" command line ** utility for accessing SQLite databases. ** | | | 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 | ** drh@hwaci.com ** http://www.hwaci.com/drh/ ** ************************************************************************* ** This file contains code to implement the "sqlite" command line ** utility for accessing SQLite databases. ** ** $Id: shell.c,v 1.2 2000/05/29 17:44:25 drh Exp $ */ #include <stdlib.h> #include <string.h> #include <stdio.h> #include "sqlite.h" #include <unistd.h> #include <ctype.h> |
︙ | ︙ | |||
217 218 219 220 221 222 223 | struct callback_data data; char *zErrMsg = 0; char zSql[1000]; memcpy(&data, p, sizeof(data)); data.showHeader = 0; data.mode = MODE_List; sprintf(zSql, "SELECT name FROM sqlite_master " | | > | 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 | struct callback_data data; char *zErrMsg = 0; char zSql[1000]; memcpy(&data, p, sizeof(data)); data.showHeader = 0; data.mode = MODE_List; sprintf(zSql, "SELECT name FROM sqlite_master " "WHERE type='index' AND tbl_name='%.00s' " "ORDER BY name", azArg[1]); sqlite_exec(db, zSql, callback, &data, &zErrMsg); if( zErrMsg ){ fprintf(stderr,"Error: %s\n", zErrMsg); free(zErrMsg); } }else |
︙ | ︙ | |||
279 280 281 282 283 284 285 | if( c=='s' && strncmp(azArg[0], "separator", n)==0 && nArg==2 ){ sprintf(p->separator, "%.*s", (int)ArraySize(p->separator)-1, azArg[1]); }else if( c=='t' && strncmp(azArg[0], "tables", n)==0 ){ struct callback_data data; char *zErrMsg = 0; | > | | 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 | if( c=='s' && strncmp(azArg[0], "separator", n)==0 && nArg==2 ){ sprintf(p->separator, "%.*s", (int)ArraySize(p->separator)-1, azArg[1]); }else if( c=='t' && strncmp(azArg[0], "tables", n)==0 ){ struct callback_data data; char *zErrMsg = 0; static char zSql[] = "SELECT name FROM sqlite_master WHERE type='table' ORDER BY name"; memcpy(&data, p, sizeof(data)); data.showHeader = 0; data.mode = MODE_List; sqlite_exec(db, zSql, callback, &data, &zErrMsg); if( zErrMsg ){ fprintf(stderr,"Error: %s\n", zErrMsg); free(zErrMsg); |
︙ | ︙ | |||
340 341 342 343 344 345 346 347 348 349 350 351 352 353 | data.showHeader = 0; if( istty ){ printf( "Enter \".help\" for instructions\n" ); } while( (zLine = readline(istty ? (zSql==0 ? "sql> " : ".... ") : 0))!=0 ){ if( zLine && zLine[0]=='.' ){ do_meta_command(zLine, db, &data); free(zLine); continue; } if( zSql==0 ){ nSql = strlen(zLine); | > | 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 | data.showHeader = 0; if( istty ){ printf( "Enter \".help\" for instructions\n" ); } while( (zLine = readline(istty ? (zSql==0 ? "sql> " : ".... ") : 0))!=0 ){ add_history(zLine); if( zLine && zLine[0]=='.' ){ do_meta_command(zLine, db, &data); free(zLine); continue; } if( zSql==0 ){ nSql = strlen(zLine); |
︙ | ︙ |
Changes to src/util.c.
︙ | ︙ | |||
22 23 24 25 26 27 28 | ** ************************************************************************* ** Utility functions used throughout sqlite. ** ** This file contains functions for allocating memory, comparing ** strings, and stuff like that. ** | | > | > > > | 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 | ** ************************************************************************* ** Utility functions used throughout sqlite. ** ** This file contains functions for allocating memory, comparing ** strings, and stuff like that. ** ** $Id: util.c,v 1.2 2000/05/29 17:44:25 drh Exp $ */ #include "sqliteInt.h" #include <stdarg.h> #include <ctype.h> /* ** Allocate new memory and set it to zero. Return NULL if ** no memory is available. */ void *sqliteMalloc(int n){ void *p = malloc(n); /* printf("alloc 0x%x size: %d bytes\n", (int)p, n); */ if( p==0 ) return 0; memset(p, 0, n); return p; } /* ** Free memory previously obtained from sqliteMalloc() */ void sqliteFree(void *p){ if( p ){ /* printf("free 0x%x\n", (int)p); */ free(p); } } /* ** Resize a prior allocation. If p==0, then this routine ** works just like sqliteMalloc(). If n==0, then this routine ** works just like sqliteFree(). */ |
︙ | ︙ |
Added www/index.tcl.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 | # # Run this TCL script to generate HTML for the index.html file. # set rcsid {$Id: index.tcl,v 1.1 2000/05/29 17:44:25 drh Exp $} puts {<html> <head><title>SQLite: An SQL Frontend For GDBM</title></head> <body bgcolor=white> <h1 align=center>SQLite: An SQL Frontend For GDBM</h1> <p align=center>} puts "Version 0.1 (alpha)<br />" puts "Last modified [lrange $rcsid 3 4]" puts {</p>} puts {<h2>Introduction</h2> <p>SQLite is a C library that implements an SQL frontend to GDBM. SQLite is intended for use in standalone programs that need to use an SQL database but which do not have access to a full-blown SQL RDBMS.</p> <p>The C interface to SQLite is very simple, consisting of only four functions and a single opaque data structure. A Tcl interface to SQLite is also available and is included in the source tree. Interfaces for perl and python may be supplied in future releases.</p> <p>There is a standalone C program named "sqlite" that can be used to interactively create, update and/or query an SQLite database. The sources to the sqlite program are part of the source tree and can be used as an example of how to interact with the SQLite C library.</p> <p>SQLite does not try to implement every feature of SQL. But it does strive to implement to most commonly used features. SQLite currently understands the following SQL commands:</p> <p> <ul> <li>CREATE TABLE</li> <li>CREATE INDEX</li> <li>DROP TABLE</li> <li>DROP INDEX</li> <li>INSERT INTO</li> <li>UPDATE</li> <li>SELECT</li> <li>DELETE FROM</li> </ul> </p> <p>SQLite does not (at present) implement any of these features:</p> <p> <ul> <li>ALTER TABLE</li> <li>The GROUP BY or HAVING clauses of a SELECT</li> <li>The LIKE or IN operators of expressions</li> <li>Constraints</li> <li>Transactions or rollback</li> </ul> </p> <H2>Status</h2> <p>The current version of SQLite should be considered "alpha" software. It is incomplete and is known to contain bugs. The software is subject to incompatible changes with each release. You should not use SQLite in its present form in production software.</p> <p>The purpose of releasing SQLite before it is ready is to evoke public comment and criticism of the software. If you find bugs or have any thoughts on how to make SQLite better, or would like to contribute code or patches to SQLite, please join the mailing (see below) and let us know.</p> <p>SQLite has so far been tested only on RedHat 6.0 Linux. But we know of no reason why it will not work on any other Unix platform, or on Windows95/98/NT.</p> } puts {<h2>Mailing List</h2> <p>A mailing list has been set up on eGroups for discussion of SQLite design issues or for asking questions about SQLite.</p> <center> <a href="http://www.egroups.com/subscribe/sqlite"> <img src="http://www.egroups.com/img/ui/join.gif" border=0 /><br /> Click to subscribe to sqlite</a> </center>} puts {<h2>Download</h2> <p>You can download a tarball containing complete SQLite source code at <a href="sqlite.tar.gz">sqlite.tar.gz</a>.} puts "This is a [file size sqlite.tar.gz] byte download. The tarball was last modified at [clock format [file mtime sqlite.tar.gz]]" puts {</p>} puts {<h2>Related Sites</h2> <ul> <li><p>The cannonical site for GDBM is <a href="http://www.gnu.org/software/gdbm/gdbm.html"> http://www.gnu.org/software/gdbm/gdbm.html</a></p></li> <li><p>Someday, we would like to port SQLite to work with the Berkeley DB library in addition to GDBM. For information about the Berkeley DB library, see <a href="http://www.sleepcat.com/">http://www.sleepycat.com</a> </p></li> </ul>} puts { <p><hr /></p> <p> <a href="../index.html"><img src="/goback.jpg" border=0 /> More Open Source Software</a> from Hwaci. </p> </body></html>} |
Added www/sqlite.tcl.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 | # # Run this Tcl script to generate the sqlite.html file. # set rcsid {$Id: sqlite.tcl,v 1.1 2000/05/29 17:44:26 drh Exp $} puts {<html> <head> <title>sqlite: A program of interacting with SQLite databases</title> </head> <body bgcolor=white> <h1 align=center> <tt>sqlite</tt>: A program to administer SQLite databases </h1>} puts "<p align=center>(This page was last modified on [lrange $rcsid 3 4])</p>" puts { <p>The SQLite library includes a simple command-line utility named <b>sqlite</b> that allows the user to manually enter and execute SQL commands against an SQLite database. This document provides a brief introduction on how to use <b>sqlite</b>. <h2>Getting Started</h2> <p>To start the <b>sqlite</b> program, just type "sqlite" followed by the name of an SQLite database. An SQLite database is really just a directory full of GDBM files, so the argument to the sqlite command should really be the name of a directory on your disk. If that directory did not previously contain an SQLite database, a new one is created for you automatically. The <b>sqlite</b> program will prompt you to enter SQL. Type in SQL statements (terminated by a semicolon, press "Enter" and the SQL will be executed. It's as simple as that!</p> <p>For example, to create a new SQLite database named "ex1" with a single table named "tbl1", you might do this:</p> } proc Code {body} { puts {<blockquote><pre>} regsub -all {&} [string trim $body] {\&} body regsub -all {>} $body {\>} body regsub -all {<} $body {\<} body regsub -all {\(\(\(} $body {<font color="#00671f"><i>} body regsub -all {\)\)\)} $body {</i></font>} body puts $body puts {</pre></blockquote>} } Code { $ (((mkdir ex1))) $ (((sqlite ex1))) Enter ".help" for instructions sql> (((create table tbl1(one varchar(10), two smallint);))) sql> (((insert into tbl1 values('hello!',10);))) sql> (((insert into tbl1 values('goodbye', 20);))) sql> (((select * from tbl1;))) one = hello! two = 10 one = goodbye two = 20 sql> } puts { <p>(In the example above, and in all subsequent examples, the commands you type are shown with a green tint in an italic font and the responses from the computer are shown in black with a constant-width font.)</p> <p>You can terminate the sqlite program by typing your systems End-Of-File character (usually a Control-D) or the interrupt character (usually a Control-C).</p> <p>Make sure you type a semicolon at the end of each SQL command. The sqlite looks for a semicolon to know when your SQL command is complete. If you omit the semicolon, sqlite will give you a continuation prompt and wait for you to enter more text to be added to the current SQL command. This feature allows you to enter SQL commands that span multiple lines. For example:</p> } Code { sql> (((CREATE TABLE tbl2 ())) .... ((( f1 varchar(30) primary key,))) .... ((( f2 text,))) .... ((( f3 real))) .... ((();))) sql> } puts { <p>If you exit sqlite and look at the contents of the directory "ex1" you'll see that it now contains two files: <b>sqlite_master.tcl</b> and <b>tbl1.tbl</b>. The <b>tbl1.tbl</b> file contains all the data for table "tbl1" in your database. The file <b>sqlite_master.tbl</b> is a special table found on all SQLite databases that records information about all other tables and indices. In general, an SQLite database will contain one "*.tbl" file for each table and index in your database, plus the extra "sqlite_master.tbl" file used to store the database schema.</p> <h2>Aside: Querying the SQLITE_MASTER table</h2> <p>You can execute "SELECT" statements against the special sqlite_master table just like any other table in an SQLite database. For example:</p> } Code { $ (((sqlite ex1))) Enter ".help" for instructions sql> (((select * from sqlite_master;))) type = table name = tbl1 tbl_name = tbl1 sql = create table tbl1(one varchar(10), two smallint) sql> } puts { <p> But you cannot execute DROP TABLE, UPDATE, INSERT or DELETE against the sqlite_master table. At least not directly. The sqlite_master table is updated automatically as you create or drop tables and indices from the database, but you can not modify sqlite_master directly. </p> <h2>Special commands to sqlite</h2> <p> Most of the time, sqlite just reads lines of input and passes them on to the SQLite library for execution. But if an input line begins with a dot ("."), then that line is intercepted and interpreted by the sqlite program itself. These "dot commands" are typically used to change the output format of queries, or to execute certain command prepackaged query statements. </p> <p> For a listing of the available dot commands, you can enter ".help" at any time. For example: </p>} Code { sql> (((.help))) .exit Exit this program .explain Set output mode suitable for EXPLAIN .header ON|OFF Turn display of headers on or off .help Show this message .indices TABLE Show names of all indices on TABLE .mode MODE Set mode to one of "line", "column", or "list" .output FILENAME Send output to FILENAME .output stdout Send output to the screen .schema ?TABLE? Show the CREATE statements .separator STRING Change separator string for "list" mode .tables List names all tables in the database .width NUM NUM ... Set column widths for "column" mode sql> } puts { <h2>Changing Output Formats</h2> <p>The sqlite program is able to show the results of a query in three different formats: "line", "column", and "list". You can use the ".mode" dot command to switch between these three output formats.</p> <p>In "line" mode (the default), each field in a record of the database is shown on a line by itself. Each line consists of the field name, an equal sign and the field data. Successive records are separated by a blank line. Here is an example of line mode output:</p>} Code { sql> (((.mode line))) sql> (((select * from tbl1;))) one = hello two = 10 one = goodbye two = 20 sql> } puts { <p>In column mode, each record is shown on a separate line with the data aligned in columns. For example:</p>} Code { sql> (((.mode column))) sql> (((select * from tbl1;))) one two ---------- ---------- hello 10 goodbye 20 sql> } puts { <p>By default, each column is 10 characters wide. Data that is too wide to fit in a column is trucated. You can adjust the column widths using the ".width" command. Like this:</p>} Code { sql> (((.width 12 6))) sql> (((select * from tbl1;))) one two ------------ ------ hello 10 goodbye 20 sql> } puts { <p>The ".width" command in the example above set the width of the first column to 12 and the width of the second column to 6. All other column widths were unaltered. You can gives as many arguments to ".width" as necessary to specify the widths of as many columns as are in your query results.</p> <p>The column labels that appear on the first two lines of output can be turned on and off using the ".header" dot command. In the examples above, the column labels are on. To turn them off you could do this:</p>} Code { sql> (((.header off))) sql> (((select * from tbl1;))) hello 10 goodbye 20 sql> } puts { <p>The third output mode supported by sqlite is called "list". In list mode, each record of a query result is written on one line of output and each field within that record is separated by a specific separator string. The default separator is a pipe symbolc ("|"). List mode is especially useful when you are going to send the output of a query to another program (such as AWK) for additional process.</p>} Code { sql> (((.mode list))) sql> (((select * from tbl1;))) hello|10 goodbye|20 sql> } puts { <p>You can use the ".separator" dot command to change the separator for list mode. For example, to change the separator to a comma and a space, you could do this:</p>} Code { sql> (((.separator ", "))) sql> (((select * from tbl1;))) hello, 10 goodbye, 20 sql> } puts { <h2>Writing results to a file</h2> <p>By default, sqlite sends query results to standard output. You can change this using the ".output" command. Just put the name of an output file as an argument to the .output command and all subsequent query results will be written to that file. Use ".output stdout" to begin writing to standard output again. For example:</p>} Code { sql> (((.mode list))) sql> (((.separator |))) sql> (((.output test_file_1.txt))) sql> (((select * from tbl1;))) sql> (((.exit $ (((cat test_file_1.txt))) hello|10 goodbye|20 $ } puts { <h2>Querying the database schema</h2> <p>The sqlite program provides several convenience commands that are useful for looking at the schema of the database. There is nothing that these commands do that cannot be done by some other means. These commands are provided purely as a shortcut.</p> <p>For example, to see a list of the tables in the database, you can enter ".tables".</p> } Code { sql> (((.tables))) tbl1 tbl2 sql> } puts { <p>The ".tables" command is the same as setting list mode then executing the following query:</p> <blockquote><pre> SELECT name FROM sqlite_master WHERE type='table' ORDER BY name; </pre></blockquote> <p>In fact, if you look at the source code to the sqlite program (found in the source tree in the file src/shell.c) you'll find exactly the above query.</p> <p>The ".indices" command works in a similar way to list all of the indices for a particular table. The ".indices" command takes a single argument which is the name of the table for which the indices are desired. Last, but not least, is the ".schema" command. With no arguments, the ".schema" command shows the original CREATE TABLE and CREATE INDEX statements that were used to build the current database. If you give the name of a table to ".schema", it shows the original CREATE statement used to make that table and all if its indices. We have:</p>} Code { sql> (((.schema))) create table tbl1(one varchar(10), two smallint) CREATE TABLE tbl2 ( f1 varchar(30) primary key, f2 text, f3 real ) sql> (((.schema tbl2))) CREATE TABLE tbl2 ( f1 varchar(30) primary key, f2 text, f3 real ) sql> } puts { <p>The ".schema" command accomplishes the same thing as setting list mode, then entering the following query:</p> <blockquote><pre> SELECT sql FROM sqlite_master ORDER BY tbl_name, type DESC, name </pre></blockquote> <h2>Other Dot Commands</h2> <p>The ".explain" dot command can be used to set the output mode to "column" and to set the column widths to values that are reasonable for looking at the output of an EXPLAIN command. The EXPLAIN command is an SQLite-specific command that is useful for debugging. If any regular SQL is prefaced by EXPLAIN, then the SQL command is parsed and analyized but is not executed. Instead, the sequence of virtual machine instructions that would have been used to execute the SQL command are returned like a query result. For example:</p>} Code { sql> (((.explain))) sql> (((explain delete from tbl1 where two<20;))) addr opcode p1 p2 p3 ---- ------------ ----- ----- ------------------------------------- 0 ListOpen 0 0 1 Open 0 0 tbl1 2 Next 0 9 3 Field 0 1 4 Integer 20 0 5 Ge 0 2 6 Key 0 0 7 ListWrite 0 0 8 Goto 0 2 9 Noop 0 0 10 ListRewind 0 0 11 ListRead 0 14 12 Delete 0 0 13 Goto 0 11 14 ListClose 0 0 } puts { <p>And finally, we mention the ".exit" command which causes the sqlite program to exit.</p> <h2>Using sqlite in a shell script</h2> <p> One way to use sqlite in a shell script is to use "echo" or "cat" to generate a sequence of commands in a file, then invoke sqlite while redirecting input from the generated command file. This works fine and is appropriate in many circumstances. But as an added convenience, sqlite allows a single SQL command to be entered on the command line as a second argument after the database name. When the sqlite program is launched with two arguments, the second argument is passed to the SQLite library for processing, the query results are printed on standard output in list mode, and the program exits. This mechanism is designed to make sqlite easy to use in conjunction with programs like "awk". For example:</p>} Code { $ (((sqlite ex1 'select * from tbl1' |))) > ((( awk '{printf "<tr><td>%s<td>%s\n",$1,$2 }'))) <tr><td>hello<td>10 <tr><td>goodbye<td>20 $ } puts { <h2>Compiling the sqlite program from sources</h2> <p> The sqlite program is built automatically when you compile the sqlite library. Just get a copy of the source tree, run "configure" and then "make".</p> } puts { <p><hr /></p> <p><a href="index.html"><img src="/goback.jpg" border=0 /> Back to the SQLite Home Page</a> </p> </body></html>} |