aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
| | * | In the name resolver when SQLITE_ALLOW_ROWID_IN_INDEX is enabled, if theredrh2024-03-19
| | | | | | | | | | | | | | | | | | | | | | | | are multiple views that might resolve to the "rowid" but only one real table, then use that one real table and ignore the views. FossilOrigin-Name: 8fcea4cdfc89dd78eca5e7f62aa31aff0e296f41e79349d3af1cc3a2bc4d77c6
| | * | Update tests to work with SQLITE_ALLOW_ROWID_IN_VIEW.dan2024-03-19
| | | | | | | | | | | | FossilOrigin-Name: 495b8c7b08b998ddfe2ad055703f058c768e7e94014952e5cd8a81c7c1515cb1
| | * | Improvements to the first check-in on this branch, causing less collateraldrh2024-03-19
| | | | | | | | | | | | | | | | | | | | damage. FossilOrigin-Name: 7bc882897b6910f93695ad372445df7791b096412089ccbcd4fde365c62fa074
| | * | On second thought, change SQLITE_TESTCTRL_ROWID_IN_VIEW into a start-timedrh2024-03-19
| | | | | | | | | | | | | | | | | | | | option SQLITE_CONFIG_NO_ROWID_IN_VIEW. FossilOrigin-Name: b8e045c9e1d098d116f8745704b10ed76569d4b063c0b81cce16bc136930755d
| | * | When compiled with SQLITE_ALLOW_ROWID_IN_VIEW, rowid-in-view is on by defaultdrh2024-03-19
| | | | | | | | | | | | | | | | | | | | | | | | but can now be turned off using SQLITE_TESTCTRL_ROWID_IN_VIEW. Without the compile-time option, rowid-in-view is always off. FossilOrigin-Name: 8a6196ab29052071be753c5c77ac945c2d62ecc8019c6160f954eafe34ab05a8
| | * | First steps toward getting -DSQLITE_ALLOW_ROWID_IN_VIEW to work again. Thatdrh2024-03-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | compile-time option is untested, undocumented, and unsupported. But it was mentioned in the release notes for version 3.36.0, so I think that means we need to support it forever. FossilOrigin-Name: 7c46ff640247584f1ea260c062de29a0e49f649d1894a526574c1a479006a1fc
| * | | Make sure the new u1.nRow value is copied when making a copy of a SrcItemdrh2024-03-19
| | |/ | |/| | | | | | | | | | object. This fixes a problem in [ac6f095e13e43d66] from yesterady. FossilOrigin-Name: 262f8f9d80d37160e4126634b99aa48fce2073e61f6365e8bdbe1cc4fa560a96
| * | Fix another problem from [c63e26e705f5e967] involving infinities and thedrh2024-03-19
| |/ | | | | | | | | | | Kahan-Babushka-Neumaier summation algorithm. Problem reported by [forum:/forumpost/23b8688ef4|forum post 23b8688ef4]. FossilOrigin-Name: 45d272ef38d5ee6189f81369aefb8e3ac35868a67687012d93c84f2bbc42520a
| * Fix harmless compiler (scan-build) warnings.drh2024-03-18
| | | | | | FossilOrigin-Name: c86f9f2a15ffc726b7f0d9bba5a8c4dfdaeea6a297e0b591c554fff3d1fe6e1c
| * Allow the VALUES-as-coroutine optimization to be applied to later rows ofdrh2024-03-18
| | | | | | | | | | a VALUES clause even if earlier rows do not qualify. FossilOrigin-Name: 9a47ea7f0f675f7bf4710901487ce34c7689e618cd1d8b9f94f0ff7ebc3f2841
| * Add assert() statements to validate access to the SrcItem.u1.nRow union member.drh2024-03-18
| | | | | | FossilOrigin-Name: 21f616d9b948efca441f8d45d0a95f4c052ce8b6daec7fa582ad9a00b82ca570
| * Fix the patch at [10ee6fcba08ab128] so that it works on reduced-size Exprdrh2024-03-18
| | | | | | | | | | nodes. FossilOrigin-Name: 260bd764c3f2d6d067adb9cd0045b7c24d5e00b02ab2735b1cba455a6143ff4c
| * Improvements to EXPLAIN QUERY PLAN output for multi-row VALUES claues.drh2024-03-18
| | | | | | FossilOrigin-Name: ac6f095e13e43d66c06552c8b01f6bec3407c9d41a34c4cdb0be57b0b828ad0d
| * Ensure the database schema has been loaded and the database encoding gleaned ↵dan2024-03-18
| | | | | | | | | | before beginning to code a multi-row VALUES clause. FossilOrigin-Name: 2ff476eb3d1f4a2146f4a48b57895a00a3ff5beb29afa679ae53ea58cac07c76
| * Fix a problem caused by a non-aggregate function with an OVER clause in a ↵dan2024-03-18
| | | | | | | | | | multi-row VALUES clause. FossilOrigin-Name: 10ee6fcba08ab1281235197602148fe062560e1d5034a477b8e7b574dd3e2907
| * Omit the "noop(X)" test SQL function. Accomplish the same thing usingdrh2024-03-17
| | | | | | | | | | the idiom: "coalesce(X,random())". FossilOrigin-Name: 0eb2fbb8910e7a372c50db3ae44238d7b161f0e45858b74061b5228aec5fcc7e
| * Add an ALWAYS on an unreachable branch.drh2024-03-17
| | | | | | FossilOrigin-Name: 0dce6211690210e802545cbca9b3375e07075e117fad3f8c921879da7671d981
| * A formerly impossible case has now become possible because of the newdrh2024-03-16
| | | | | | | | | | ExprIsConstant enhancements. So deal with that. FossilOrigin-Name: 9ba3cff9d48fe8fc8a0a51291169599209d464465e44bdfd60058fd1e314a2b1
| * Further expand the scope of usage for the enhacement to expr-is-constant.drh2024-03-16
| | | | | | FossilOrigin-Name: d7eadcf7dd089f0f4aa963c58f0df32edd951368c9906375fd62b0a61cd393b8
| * Assert that the eCode is always non-zero upon entry into exprNodeIsConstant().drh2024-03-16
| | | | | | FossilOrigin-Name: f71b28f6713126745bca53e098dfe3444d4235d6a2b87ced5b333a7f0ee79be8
| * Activate the enhanced constant-expression for thedrh2024-03-16
| | | | | | | | | | [constant propagation optimization](/info/f4229707ac08d66c). FossilOrigin-Name: 92afea38881a1a4f266c79ddc6e1027cf17c288dcc8f7e7d50466899ac0054c4
| * Extend the scope expr-is-constant for function to cover the IN-to-EQdrh2024-03-16
| | | | | | | | | | optimization. FossilOrigin-Name: dae669245c86021bcd28716aff6e316257cc8075d02081745d4b7de17f8ad553
| * Fix exprNodeIsConstantFunction() so that it returns WRC_Continue, not ↵dan2024-03-16
| | | | | | | | | | WRC_Abort, if the function really is constant. FossilOrigin-Name: d85dd4de2d0989127e0ae6a2eec9d83a577777f8d5ba40700084a0b498016634
| * Enhance the sqlite3ExprIsConstant() function so that it recognizesdrh2024-03-16
| | | | | | | | | | | | constant functions. So far the enhancement only applies to the multi-row VALUES clause, but it could possibly be applied in many other places. FossilOrigin-Name: c9e0488c6c0135932b6e76b0f3f3acd69ef65327e0a54daa59777f35da1aef26
| * Fix a problem with ALTER TABLE and correlated multi-row VALUES clauses.dan2024-03-14
| | | | | | FossilOrigin-Name: d543c829ef74dbd64105bd757ca660e4f02e9ce562be4f1688a701fa535351c4
| * Fix a problem handling "INSERT INTO ... SELECT ... UNION VALUES(...), (...)" ↵dan2024-03-14
| | | | | | | | | | and similar statements. FossilOrigin-Name: e8a2a8198a97046ff376bc5d38e4bc0a24fcac79f5a0dadb9d29d953a862a012
| * Avoid some OP_SCopy instructions in "INSERT INTO .. VALUES" statements that ↵dan2024-03-14
| | | | | | | | | | insert more than one row in cases where the VALUES clause contains a value for all columns of the table. FossilOrigin-Name: 988f0ea70cd21b3194011e0cd1ddd4990a07669e0fd9c37afa48f69698ab7212
| * Change the way parse.y handles multi-row VALUES clauses to save a few cycles.dan2024-03-13
| | | | | | FossilOrigin-Name: 88d5bc91a52675d2a83748b79ad50de0e9732b2afd23107627bdc604f744d275
| * Remove unreachable code from this branch.dan2024-03-13
| | | | | | FossilOrigin-Name: 657c7b4f9df53e041a33cfad00ee2f507ac09c97a2ae61164bd189d660d167da
| * Fix some OOM handling problems on this branch.dan2024-03-13
| | | | | | FossilOrigin-Name: 2085c7f12a3916ec883c31795e29f2e2b6641c30ecf748cce9bff7b13b061d1f
| * Ensure that if a multi-row VALUES cannot be coded while being parsed, the ↵dan2024-03-13
| | | | | | | | | | SF_MultiValue flag is correctly set. FossilOrigin-Name: 94791824a6f04782aac6bc16c182685e2d6ebf5c688dc9f8d59e479c6fd5a40e
| * Avoid creating a co-routine incrementally for a VALUES clause that has ↵dan2024-03-13
| | | | | | | | | | affinities other than NONE. FossilOrigin-Name: 4229b12b327b05561dcf49b8585a66467d17d4e998b14eff65eb886f2434b53c
| * Correctly initialize the SrcItem.iCursor field to -1 when creating a ↵dan2024-03-12
| | | | | | | | | | co-routine from a multi-values VALUES clause. FossilOrigin-Name: c32953ff6d72910815eaff29ab1b790c412e1a741d02c03c5911dda0c08e5130
| * Attempt to reduce the memory used by VALUES clauses in as many statements as ↵dan2024-03-11
| | | | | | | | | | possible, not just INSERT. This branch still has problems. FossilOrigin-Name: 17d1f7cfabc7593d0725051b0c7c9619a23a482265f30f15ab9493fef5caeeb0
| * Fix the ".import" command in the CLI so that it works correctly with tablesdrh2024-03-11
| | | | | | | | | | | | that contain computed columns. [forum:/forumpost/ca014d7358|forum post ca014d7358]. FossilOrigin-Name: 95a9c88b258f18ac671a4c712603931167cc8bd0b86e41481b200c08043338b5
| * Fix the .expert command in the shell so that it does not leak memory if notdrh2024-03-09
| | | | | | | | | | followed by SQL and so that it works with reverse_unordered_selects. FossilOrigin-Name: 7ead022edaf7a0cd6a8976a1261246084975c9a5be5c893f6c751bb5f963ac0f
| * The NOT NULL strength reduction optimization from [de9c86c9e4cdb34f] shoulddrh2024-03-08
| | | | | | | | | | | | | | | | be applied to the WHERE clause only. Otherwise, the operand of the IS NULL or IS NOT NULL operator might be a reference to a bare column of an aggregate table, and we can't tell if it is NULL or not based only on its NOT NULL attribute. [forum:/forumpost/440f2a2f17|Forum post 440f2a2f17]. FossilOrigin-Name: 51704feae224eff601db5607f8651da11b3c2ed8a58ffe5b6ee8260cab50695b
| * One of the assert()s added by the previous check-in was not quite correct.drh2024-03-08
| | | | | | | | | | This commit fixes it. FossilOrigin-Name: d401358329f5a70f9a0b9b033609a4db2af89b83c6b40242be0c76f3d6474def
| * Add new assert() statements, which if they had existed three years ago,drh2024-03-08
| | | | | | | | | | would have detected the code generator problem fixed by the previous check-in. FossilOrigin-Name: 166d1e5d26ef88e995f44182144891f60bd51c1aa585b4a148f01a920b2a8eea
| * Silently ignore redundant ON CONFLICT clauses in an UPSERT. Only the firstdrh2024-03-08
| | | | | | | | | | | | | | ON CONFLICT for each index is active. Do not issue an error, since that might break legacy queries. But ignore the redundant ON CONFLICT clauses to prevent problems such as described in [forum:/forumpost/919c6579c8|forum post 919c6579c8]. FossilOrigin-Name: d0ea6b6ba64dba9d68c2b391ccf1171ea96fcdd7409dafdb2b697accb00246b8
| * Do not allow the query planner to be tricked into thinking that an index on adrh2024-03-07
| | | | | | | | | | | | | | constant expression might be useful for something. Problem reported on [forum:/forumpost/ecdfc02339|forum post ecdfc02339]. This is a follow-up to the fixes at [44200596aa943963] and [2d2b91cc0f6fed8c]. FossilOrigin-Name: 720ce06d93a9e4cc25c34c873c82165d8801f208c22701e51538f3210de84f65
| * Add the json_pretty() SQL function.drh2024-03-06
| |\ | | | | | | FossilOrigin-Name: ceb51c1cc36dfb78db8f2be042a0d74ab9a877d14a53dadf876d09e1a0616d6a
| | * Add the json_pretty(J) function for pretty-printing of JSON. An optionaldrh2024-03-06
| | | | | | | | | | | | | | | | | | 2nd argument is text used for indentation, with a default value being four spaces. FossilOrigin-Name: 39552bd36c06fe9ee346cb71e0659baceccde031b67c0974f2dd14eb11ebc055
| * | Work around obscure floating point issue seen with older versions of MSVC.mistachkin2024-03-06
| |/ | | | | FossilOrigin-Name: 42d39f9140cc315df04b048f3811311fa50b51e1831d6cdf982fbce029778e43
| * Remove code that added a P4 parameter to the OP_Variable opcode. This is no ↵dan2024-03-05
| | | | | | | | | | longer required. FossilOrigin-Name: dd5977c9a8a418be3fbd646d74933996381099a9263a02eb4a990f0084463dc1
| * Reformulate [34439fe3aeea7cbb] slightly to resolve a false-positive OOM ↵stephan2024-03-05
| | | | | | | | | | reported in [forum:2eadfe94e3|forum post 2eadfe94e3]. FossilOrigin-Name: 8290646792bc5411112b0c01dc5ac0837743056a7679725ee2edefef2e10d146
| * The value returned by the json_each.json field needs to survive longer thandrh2024-03-05
| | | | | | | | | | | | the json_each virtual table itself, in the event that the value is used in an aggregate expression. dbsqlfuzz 5120bd0b3bb0b73eebbcb79ac37c6b0663fccad6 FossilOrigin-Name: 952ed71b9b61e79fe807ac3134bdfa7c94a415e02f13f94440a34d6d548d171e
| * /fiddle: before resetting a db, roll back any transactions (resolves problem ↵stephan2024-03-05
| | | | | | | | | | reported in [forum:0b41a25d65|forum post 0b41a25d65]) and remove an obsolete/broken reference to a long-gone API which could cause initialization to fail prematurely. FossilOrigin-Name: ee164ca73cf4151b1a1bf351729afa9b0ec95bd5004a5d5bfce3ed46268bfbf3
| * Fix a compiler warning in date.c. Update makefiles to include all necessarydrh2024-03-04
| | | | | | | | | | dependencies for building shell.c. FossilOrigin-Name: 178b7d46f9c8e1694ed6f506d2785a9f5c49e2b428e04c8096d557cc1b5c9680
| * Adjust date/time functions so that they do a better job of keeping trackdrh2024-03-04
| | | | | | | | | | | | | | | | | | | | of whether the current time is UTC or localtime, and no-op the 'utc' and 'localtime' modifiers accordingly. See [forum:/info/e7a939e074|forum post e7a939e074]. Also add the datedebug() function, available only under -DSQLITE_DEBUG, for improved visibility of the DateTime object during debugging and testing. FossilOrigin-Name: dc569683748354a6db83438904422e802d3ea780775c48da85b474fff03ca8a1
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-06 04:33:45 +0000