# Documentation Source Text

Check-in [8c65dc2deb]

Overview
Comment: Fix typos detected by spellcheck. Tarball | ZIP archive | SQL archive family | ancestors | descendants | both | files | file ages | folders 8c65dc2debb83d37923bd57de0930a9ccd9c6b566f952c0a2d5088e994aa9ca4 drh 2019-02-07 14:31:19
Context
 2019-02-07 16:59 Update the size and performance graph spreadsheet. (check-in: 5c6358b7e1 user: drh tags: trunk) 14:31 Fix typos detected by spellcheck. (check-in: 8c65dc2deb user: drh tags: trunk) 13:59 Add back the sponsors section to the front page. (check-in: 3b7ad43873 user: drh tags: trunk)
Changes

Changes to pages/geopoly.in.

 ```235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 ``` ```If P is not a polygon, geopoly_bbox(P) returns NULL.

The geopoly_group_bbox(P) function is an aggregate version of geopoly_bbox(P). The geopoly_group_bbox(P) function returns the smallest rectangle that will enclose all P values seen during aggregation. hd_fragment gpoint geopoly_constains_point

The geopoly_contains_point(P,X,Y) Function

If P is a polygon, then geopoly_contains_point(P,X,Y) returns a non-zero integer if and only if the coordinate X,Y is inside or on the boundary of the polygon P. If P is not a polygon, geopoly_contains_point(P,X,Y) returns NULL. ``` ``` | ``` ```235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 ``` ```If P is not a polygon, geopoly_bbox(P) returns NULL.

The geopoly_group_bbox(P) function is an aggregate version of geopoly_bbox(P). The geopoly_group_bbox(P) function returns the smallest rectangle that will enclose all P values seen during aggregation. hd_fragment gpoint geopoly_contains_point

The geopoly_contains_point(P,X,Y) Function

If P is a polygon, then geopoly_contains_point(P,X,Y) returns a non-zero integer if and only if the coordinate X,Y is inside or on the boundary of the polygon P. If P is not a polygon, geopoly_contains_point(P,X,Y) returns NULL. ```

Changes to pages/lang.in.

 ```5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 ``` ``` statement was originally opened using the [SQLITE_OPEN_URI] flag.

The VACUUM INTO command is transactional in the sense that the generated output database is a consistent snapshot of the orgininal database. However, if the VACUUM INTO command is interrupted by a unplanned shutdown or power lose, then the generated output database might be incomplete and corrupt. Also, SQLite does not invoke fsync() or FlushFileBuffers() on the generated database to ensure that it has reached non-volatile storage before completing. ``` ``` | ``` ```5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 ``` ``` statement was originally opened using the [SQLITE_OPEN_URI] flag.

The VACUUM INTO command is transactional in the sense that the generated output database is a consistent snapshot of the original database. However, if the VACUUM INTO command is interrupted by a unplanned shutdown or power lose, then the generated output database might be incomplete and corrupt. Also, SQLite does not invoke fsync() or FlushFileBuffers() on the generated database to ensure that it has reached non-volatile storage before completing. ```

Changes to pages/pragma.in.

 ```778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 ``` ``` flag.)^ ^(When this flag is on, the [ALTER TABLE RENAME] command (for changing the name of a table) works as it did in SQLite 3.24.0 ([dateof:3.24.0]) and earlier.)^ More specifically, when this flag is on the [ALTER TABLE RENAME] command only rewrites the initial occurrence of the table name in its [CREATE TABLE] statement and in any associated [CREATE INDEX] and [CREATE TRIGGER] statements. Other references to the table are unmodifed, including:
• References to the table within the bodies of triggers and views.
• References to the table within CHECK constraints in the original CREATE TABLE statement.
• References to the table within the WHERE clauses of [partial indexes].
The default setting for this pragma is OFF, which means that all ``` ``` | ``` ```778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 ``` ``` flag.)^ ^(When this flag is on, the [ALTER TABLE RENAME] command (for changing the name of a table) works as it did in SQLite 3.24.0 ([dateof:3.24.0]) and earlier.)^ More specifically, when this flag is on the [ALTER TABLE RENAME] command only rewrites the initial occurrence of the table name in its [CREATE TABLE] statement and in any associated [CREATE INDEX] and [CREATE TRIGGER] statements. Other references to the table are unmodified, including:
• References to the table within the bodies of triggers and views.
• References to the table within CHECK constraints in the original CREATE TABLE statement.
• References to the table within the WHERE clauses of [partial indexes].
The default setting for this pragma is OFF, which means that all ```