Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Update the change log with the latest enhancements. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | bubble-generator-tkpath |
Files: | files | file ages | folders |
SHA1: |
5077172640d205a359eab156c886d5d3 |
User & Date: | drh 2015-12-31 14:06:48.761 |
Context
2016-01-02
| ||
04:16 | Cherrypick changes off of the bubble-generator-tkpath branch that were intended for trunk. Also merge in changes to the 3.9.x branch. (check-in: e2ad1111f4 user: drh tags: trunk) | |
04:14 | Further tweaks to the website. (Leaf check-in: 5619b986d5 user: drh tags: bubble-generator-tkpath) | |
2015-12-31
| ||
14:06 | Update the change log with the latest enhancements. (check-in: 5077172640 user: drh tags: bubble-generator-tkpath) | |
2015-12-22
| ||
16:03 | Modify the bubble-diagram generator script to use the TkPath extension. (check-in: 08bf2dfe78 user: chw tags: bubble-generator-tkpath) | |
Changes
Changes to pages/changes.in.
︙ | ︙ | |||
28 29 30 31 32 33 34 35 36 37 38 | <li>Enhance the [PRAGMA cache_spill] statement to accept a 32-bit integer parameter which is the threshold below which cache spilling is prohibited. <li>On unix, if a symlink to a database file is opened, then the corresponding journal files are based on the actual filename, not the symlink name. <li>Added the "--transaction" option to [sqldiff]. <li>Added the [sqlite3_db_cacheflush()] interface. <li>Added the [sqlite3_strlike()] interface. <li>Many small performance optimizations. <p><b>Portability enhancements:</b> <li>Work around a sign-exension bug in the optimizer of the HP C compiler on HP/UX. <p><b>Enhancements to makefiles:</b> | > > > > > > > > > > > > > > | | | < | 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 | <li>Enhance the [PRAGMA cache_spill] statement to accept a 32-bit integer parameter which is the threshold below which cache spilling is prohibited. <li>On unix, if a symlink to a database file is opened, then the corresponding journal files are based on the actual filename, not the symlink name. <li>Added the "--transaction" option to [sqldiff]. <li>Added the [sqlite3_db_cacheflush()] interface. <li>Added the [sqlite3_strlike()] interface. <li>When using [memory-mapped I/O] map the database file read-only so that stray pointers and/or array overruns in the application cannot accidently modify the database file. <li>Added the <em>experimental</em> [sqlite3_snapshot_get()], [sqlite3_snapshot_open()], and [sqlite3_snapshot_free()] interfaces. These are subject to change or removal in a subsequent release. <li>Enhance the ['utc' modifier] in the [date and time functions] so that it is a no-op if the date/time is known to already be in UTC. (This is not a compatibility break since the behavior has long been documented as "undefined" in that case.) <li>Added the [json_group_array()] and [json_group_object()] SQL functions in the <li>Many small performance optimizations. <p><b>Portability enhancements:</b> <li>Work around a sign-exension bug in the optimizer of the HP C compiler on HP/UX. <p><b>Enhancements to the [command-line shell]:</b> <li>Added the ".changes ON|OFF" and ".vfsinfo dot-commands. <li>Translate between MBCS and UTF8 when running in [https://en.wikipedia.org/wiki/Cmd.exe|cmd.exe] on Windows. <p><b>Enhancements to makefiles:</b> <li>Added the --enable-editline and --enable-static-shell options to the various autoconf-generated configure scripts. <li>Omit all use of "awk" in the makefiles, to make building easier for MSVC users. <p><b>Important fixes:</b> <li>Fix inconsistent integer to floating-point comparison operations that could result in a corrupt index if the index is created on a table column that contains both large integers and floating point values of similar magnitude. Ticket [https://www.sqlite.org/src/tktview?name=38a97a87a6|38a97a87a6]. <li>Fix an infinite-loop in the query planner that could occur on |
︙ | ︙ |
Changes to pages/json1.in.
1 2 3 4 5 6 | <title>The JSON1 Extension</title> <tcl>hd_keywords json1 {the json1 extension} {JSON SQL functions}</tcl> <h2>The JSON1 Extension</h2> <p> The <b>json1</b> extension is a [loadable extension] that | | | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 | <title>The JSON1 Extension</title> <tcl>hd_keywords json1 {the json1 extension} {JSON SQL functions}</tcl> <h2>The JSON1 Extension</h2> <p> The <b>json1</b> extension is a [loadable extension] that implements thirteen [application-defined SQL functions] and two [table-valued functions] that are useful for managing [http://json.org/ | JSON] content stored in an SQLite database. These are the scalar SQL functions implemented by json1: <blockquote> <center><table border=0 cellpadding=5> <tcl> set tabcnt 0 proc tabentry {fx desc lnk} { global tabcnt |
︙ | ︙ | |||
89 90 91 92 93 94 95 96 97 98 99 100 101 102 | tabentry {json_type(json)<br>json_type(json,path)} { Return the type of a JSON string or subcomponent. } jtype tabentry {json_valid(json)} { Return true (1) if the input text is a valid JSON string } jvalid </tcl> </table></center></blockquote> <p>The [table-valued functions] implemented by this routine are: <blockquote><center><table border=0 cellpadding=5> <tcl> | > > > > > > > > > > > > > > > > | 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 | tabentry {json_type(json)<br>json_type(json,path)} { Return the type of a JSON string or subcomponent. } jtype tabentry {json_valid(json)} { Return true (1) if the input text is a valid JSON string } jvalid </tcl> </table></center></blockquote> <p>There are two aggregate SQL functions: <blockquote><center><table border=0 cellpadding=5> <tcl> tabentry {json_group_array(value)} { Return a JSON array composed of all <i>value</i> elements in the aggregation. } jgrouparray tabentry {json_group_object(name,value)} { Return a JSON object composed of all <i>name</i> and <i>value</i> pairs in the aggregation. } jgroupobject </tcl> </table></center></blockquote> <p>The [table-valued functions] implemented by this routine are: <blockquote><center><table border=0 cellpadding=5> <tcl> |
︙ | ︙ | |||
508 509 510 511 512 513 514 515 516 517 | <tcl> jexample \ {json_valid('{"x":35}')} 1 \ "json_valid('\173\"x\":35')" 0 </tcl> <tcl>hd_fragment jeach {json_each table-valued function} {json_each}</tcl> <tcl>hd_fragment jtree {json_tree table-valued function} {json_tree}</tcl> | > > > > > > > > > > > > > > > | | 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 | <tcl> jexample \ {json_valid('{"x":35}')} 1 \ "json_valid('\173\"x\":35')" 0 </tcl> <tcl> hd_fragment jgrouparray {json_group_array SQL function} \ {json_group_array} hd_fragment jgroupobject {json_group_object SQL function} \ {json_group_object} </tcl> <h3>3.10 The json_group_array() and json_group_object() aggregate SQL functions</h3> <p>The json_group_array(X) function is an [Aggregate Functions|aggregate SQL function] that returns a JSON array comprised of all X values in the aggregation. Similarly, the json_group_object(NAME,VALUE) function returns a JSON object comprised of all NAME/VALUE pairs in the aggregation. <tcl>hd_fragment jeach {json_each table-valued function} {json_each}</tcl> <tcl>hd_fragment jtree {json_tree table-valued function} {json_tree}</tcl> <h3>3.11 The json_each() and json_tree() table-valued functions</h3> <p>The json_each(X) and json_tree(X) [table-valued functions] walk the JSON value provided as their first argument and return one row for each element. The json_each(X) function only walks the immediate children of the top-level array or object or or just the top-level element itself if the top-level element is a primitive value. |
︙ | ︙ | |||
586 587 588 589 590 591 592 | <p> The "path" column is the path to the array or object container the holds the current row, or the path to the current row in the case where the iteration starts on a primitive type and thus only provides a single row of output. | | | 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 | <p> The "path" column is the path to the array or object container the holds the current row, or the path to the current row in the case where the iteration starts on a primitive type and thus only provides a single row of output. <h4>3.11.1 Examples using json_each() and json_tree()</h4> <p>Suppose the table "CREATE TABLE user(name,phone)" stores zero or more phone numbers as a JSON array object in the user.phone field. To find all users who have any phone number with a 704 area code: <blockquote><pre> SELECT DISTINCT user.name |
︙ | ︙ |
Changes to pages/lang.in.
︙ | ︙ | |||
2917 2918 2919 2920 2921 2922 2923 | separate the "unixepoch" modifier from prior DDDDDDDDDD then the behavior is undefined. Due to precision limitations imposed by the implementations use of 64-bit integers, the "unixepoch" modifier only works for dates between 0000-01-01 00:00:00 and 5352-11-01 10:52:47 (unix times of -62167219200 through 10675199167).</p> | | > | | 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 | separate the "unixepoch" modifier from prior DDDDDDDDDD then the behavior is undefined. Due to precision limitations imposed by the implementations use of 64-bit integers, the "unixepoch" modifier only works for dates between 0000-01-01 00:00:00 and 5352-11-01 10:52:47 (unix times of -62167219200 through 10675199167).</p> <tcl>hd_fragment localtime {localtime modifier} {'utc' modifier}</tcl> <p>^The "localtime" modifier (12) assumes the time string to its left is in Universal Coordinated Time (UTC) and adjusts the time string so that it displays localtime. If "localtime" follows a time that is not UTC, then the behavior is undefined. ^(The "utc" modifier is the opposite of "localtime". "utc" assumes that the string to its left is in the local timezone and adjusts that string to be in UTC.)^ If the prior string is not in localtime, then the result of "utc" is undefined.</p> <h3>Examples</h3> ^(<p>Compute the current date.<p> |
︙ | ︙ |