Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Documentation fixes. Ticket #1306. (CVS 2529) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
3dcdb7942ea9a9e5d708a198ba518310 |
User & Date: | drh 2005-06-25 19:42:38.000 |
Context
2005-06-26
| ||
17:55 | Tcl interface uses Tcl_Objs to implement user-defined functions, thus allowing BLOB values to be transferred correctly. Ticket #1304. (CVS 2530) (check-in: 514aaab3f9 user: drh tags: trunk) | |
2005-06-25
| ||
19:42 | Documentation fixes. Ticket #1306. (CVS 2529) (check-in: 3dcdb7942e user: drh tags: trunk) | |
19:31 | The TCL interface binds variables as BLOB only if they have a bytearray representation but no text representation. Ticket #1287. (CVS 2528) (check-in: 8c99dca60a user: drh tags: trunk) | |
Changes
Changes to www/lang.tcl.
1 2 3 | # # Run this Tcl script to generate the lang-*.html files. # | | | 1 2 3 4 5 6 7 8 9 10 11 | # # Run this Tcl script to generate the lang-*.html files. # set rcsid {$Id: lang.tcl,v 1.92 2005/06/25 19:42:38 drh Exp $} source common.tcl if {[llength $argv]>0} { set outputdir [lindex $argv 0] } else { set outputdir "" } |
︙ | ︙ | |||
745 746 747 748 749 750 751 | trigger programs that would of been executed are abandoned. No database changes are rolled back. If the statement that caused the trigger program to execute is itself part of a trigger program, then that trigger program resumes execution at the beginning of the next step. </p> <p>Triggers are removed using the <a href="#droptrigger">DROP TRIGGER</a> | | < | 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 | trigger programs that would of been executed are abandoned. No database changes are rolled back. If the statement that caused the trigger program to execute is itself part of a trigger program, then that trigger program resumes execution at the beginning of the next step. </p> <p>Triggers are removed using the <a href="#droptrigger">DROP TRIGGER</a> statement.</p> } Section {CREATE VIEW} {createview} Syntax {sql-command} { CREATE [TEMP | TEMPORARY] VIEW [<database-name>.] <view-name> AS <select-statement> |
︙ | ︙ | |||
778 779 780 781 782 783 784 | database name is specified, and the TEMP keyword is not present, the table is created in the main database.</p> <p>You cannot COPY, DELETE, INSERT or UPDATE a view. Views are read-only in SQLite. However, in many cases you can use a <a href="#createtrigger"> TRIGGER</a> on the view to accomplish the same thing. Views are removed with the <a href="#dropview">DROP VIEW</a> | < | | 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 | database name is specified, and the TEMP keyword is not present, the table is created in the main database.</p> <p>You cannot COPY, DELETE, INSERT or UPDATE a view. Views are read-only in SQLite. However, in many cases you can use a <a href="#createtrigger"> TRIGGER</a> on the view to accomplish the same thing. Views are removed with the <a href="#dropview">DROP VIEW</a> command.</p> } Section DELETE delete Syntax {sql-statement} { DELETE FROM [<database-name> .] <table-name> [WHERE <expr>] |
︙ | ︙ | |||
832 833 834 835 836 837 838 | <p>The DROP INDEX statement removes an index added with the <a href="#createindex"> CREATE INDEX</a> statement. The index named is completely removed from the disk. The only way to recover the index is to reenter the appropriate CREATE INDEX command.</p> <p>The DROP INDEX statement does not reduce the size of the database | > | | > | < | > | > | < | < | 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 | <p>The DROP INDEX statement removes an index added with the <a href="#createindex"> CREATE INDEX</a> statement. The index named is completely removed from the disk. The only way to recover the index is to reenter the appropriate CREATE INDEX command.</p> <p>The DROP INDEX statement does not reduce the size of the database file in the default mode. Empty space in the database is retained for later INSERTs. To remove free space in the database, use the <a href="#vacuum">VACUUM</a> command. If AUTOVACUUM mode is enabled for a database then space will be freed automatically by DROP INDEX.</p> } Section {DROP TABLE} droptable Syntax {sql-command} { DROP TABLE [<database-name>.] <table-name> } puts { <p>The DROP TABLE statement removes a table added with the <a href= "#createtable">CREATE TABLE</a> statement. The name specified is the table name. It is completely removed from the database schema and the disk file. The table can not be recovered. All indices associated with the table are also deleted.</p> <p>The DROP TABLE statement does not reduce the size of the database file in the default mode. Empty space in the database is retained for later INSERTs. To remove free space in the database, use the <a href="#vacuum">VACUUM</a> command. If AUTOVACUUM mode is enabled for a database then space will be freed automatically by DROP TABLE.</p> } Section {DROP TRIGGER} droptrigger Syntax {sql-statement} { DROP TRIGGER [<database-name> .] <trigger-name> } puts { <p>The DROP TRIGGER statement removes a trigger created by the <a href="#createtrigger">CREATE TRIGGER</a> statement. The trigger is deleted from the database schema. Note that triggers are automatically dropped when the associated table is dropped.</p> } Section {DROP VIEW} dropview Syntax {sql-command} { DROP VIEW <view-name> } puts { <p>The DROP VIEW statement removes a view created by the <a href= "#createview">CREATE VIEW</a> 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> } Section EXPLAIN explain Syntax {sql-statement} { EXPLAIN <sql-statement> |
︙ | ︙ |