Documentation Source Text

Check-in [6ec0e9720c]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Minor changes to lang_dropview.html. Add section to lang.in describing resolution of object names.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 6ec0e9720cb99a6debd3de91093c7f86ff591775
User & Date: dan 2010-11-30 12:11:43
Context
2010-11-30
18:13
Fix typos in queryplanner.in check-in: 78db9f1266 user: drh tags: trunk
12:11
Minor changes to lang_dropview.html. Add section to lang.in describing resolution of object names. check-in: 6ec0e9720c user: dan tags: trunk
2010-11-29
21:50
Explanation of the use of :-prefix host parameters for substitution in the TCL interface. check-in: af551e7e6d user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/lang.in.

1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352




























































1353
1354
1355
1356
1357
1358
1359
<tcl>
##############################################################################
Section {DROP VIEW} dropview {{DROP VIEW}}

BubbleDiagram drop-view-stmt 1
</tcl>

<p>^The DROP VIEW statement removes a view created by the
[CREATE VIEW] statement.  ^The name specified is the 
view name.  ^It is removed from the database schema, but no actual data 
in the underlying base tables is modified.</p>





























































<tcl>
##############################################################################
Section EXPLAIN explain EXPLAIN

BubbleDiagram sql-stmt
</tcl>







|
<
|
|
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>







1342
1343
1344
1345
1346
1347
1348
1349

1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
<tcl>
##############################################################################
Section {DROP VIEW} dropview {{DROP VIEW}}

BubbleDiagram drop-view-stmt 1
</tcl>

<p>^The DROP VIEW statement removes a view created by the [CREATE VIEW] 

  statement. ^The view definition is removed from the database schema, but 
  no actual data in the underlying base tables is modified.

<p>^(The view to drop is identified by the view-name and optional 
  database-name specified as part of the DROP VIEW statement. This 
  reference is resolved using the standard procedure for [object resolution].)^

<p>
  ^If the specified view cannot be found and the IF EXISTS clause is not 
  present, it is an error. ^If the specified view cannot be found and an IF
  EXISTS clause is present in the DROP VIEW statement, then the statement
  is a no-op.


<tcl>
##############################################################################
Section {Database Object Name Resolution} {naming} {{object resolution}}
</tcl>

<p>
  In SQLite, a database object (a table, index, trigger or view) is identified
  by the name of the object and the name of the database that it resides in. 
  Database objects may reside in the main database, the temp database, or in
  an [ATTACH|attached database].

<p>
  The syntax of the [DROP TABLE], [DROP INDEX], [DROP VIEW], [DROP TRIGGER],
  [REINDEX], [ALTER TABLE] and many other commands all permit the user to
  specify a database object either by its name alone, or by a combination of
  its name and the name of its database. ^(If no database is specified as part
  of the object reference, then SQLite searches the main, temp and all attached
  databases for an object with a matching name. The temp database is searched
  first, followed by the main database, followed all attached databases in the
  order that they were attached. The reference resolves to the first match
  found.)^ For example:

^(<pre>
      /* Add a table named 't1' to the temp, main and an attached database */
      ATTACH 'file.db' AS aux;
      CREATE TABLE t1(x, y);
      CREATE TEMP TABLE t1(x, y);
      CREATE TABLE aux.t1(x, y);

      DROP TABLE t1;         /* Drops table in temp database */
      DROP TABLE t1;         /* Drops table in main database */
      DROP TABLE t1;         /* Drops table in aux database */
</pre>)^

<p>
  ^If a database name is specified as part of an object reference, it must be
  either "main", or "temp" or the name of an attached database. ^Like other
  SQL identifiers, database names are case-insensitive. ^If a database name
  is specified, then only the named database is searched for the named object.

<p>
  Most object references may only resolve to a specific type of object (for
  example a reference that is part of a DROP TABLE statement may only resolve
  to a table object, not an index, trigger or view). However in some contexts 
  (e.g. [REINDEX]) an object reference may be resolve to more than one type
  of object. ^When searching database schemas for a named object, objects of
  types that cannot be used in the context of the reference are always 
  ignored.

<tcl>
##############################################################################
Section EXPLAIN explain EXPLAIN

BubbleDiagram sql-stmt
</tcl>