|
Revision tags: release, version-3.50.2, version-3.50.1, major-release, version-3.50.0, version-3.49.2, patch-release, version-3.44.4, version-3.49.1, version-3.49.0, major-relase, relase, version-3.48.0, version-3.47.2, version-3.47.1, version-3.47.0, version-3.46.1, version-3.46.0, version-3.45.3, version-3.44.3, version-3.45.2, version-3.45.1, vesion-3.45.1, version-3.45.0, version-3.44.2, version-3.44.1, version-3.44.0, version-3.43.2, version-3.43.1, version-3.43.0, version-3.42.0, version-3.41.2, version-3.41.1, version-3.41.0, version-3.40.1, version-3.40.0, version-3.39.4, version-3.39.3, version-3.39.2, version-3.39.1, version-3.39.0, version-3.38.5, version-3.38.4, relese, version-3.38.3, version-3.38.2, version-3.38.1, version-3.38.0, version-3.37.2, version-3.37.1 |
|
| #
66306d86 |
| 30-Dec-2021 |
drh <> |
When a table has an INTEGER PRIMARY KEY ON CONFLICT REPLACE and some other
uniqueness constraint, and it participates in an upsert on that other
constraint, ensure that code that checks for conflicts
When a table has an INTEGER PRIMARY KEY ON CONFLICT REPLACE and some other
uniqueness constraint, and it participates in an upsert on that other
constraint, ensure that code that checks for conflicts on the INTEGER PRIMARY
KEY is well-formed. Fix for the problem reported by
[forum:/forumpost/06b16b8b29f8c8c3|forum post 06b16b8b29f8c8c3].
FossilOrigin-Name: 2f09b51b1ff37bf98f958564cc1224968caa7e33147e6666b5c1ba20b2a7813b
show more ...
|
|
Revision tags: version-3.37.0, version-3.36.0, version-3.35.5, version-3.35.4, version-3.35.3, same-as-3.35.3, version-3.35.2, version-3.35.1, version-3.35.0, patch, version-3.34.1, version-3.34.0, version-3.33.0, version-3.32.3, version-3.32.2, version-3.32.1, version-3.32.0, version-3.31.1, version-3.31.0 |
|
| #
fe2a3f1d |
| 26-Dec-2019 |
drh <[email protected]> |
If an UPSERT can cause an Abort due to a constraint failure, make sure
the query planner knows this. Ticket [7c13db5c3bf74001].
FossilOrigin-Name: f14ce948662f3445a06d84d4f32d9b81143e0cffaf773d8aa4
If an UPSERT can cause an Abort due to a constraint failure, make sure
the query planner knows this. Ticket [7c13db5c3bf74001].
FossilOrigin-Name: f14ce948662f3445a06d84d4f32d9b81143e0cffaf773d8aa4d3a609bfb9682b
show more ...
|
| #
c6b24ab1 |
| 06-Dec-2019 |
drh <[email protected]> |
Do not allow UPSERT of a view.
FossilOrigin-Name: ebf897e861c19e214c57f1e73841b505182202cc8d7d39e24d5a1e5625e26b4a
|
|
Revision tags: version-3.30.1, version-3.30.0 |
|
| #
a7ce167e |
| 30-Aug-2019 |
drh <[email protected]> |
Make sure OP_RealAffinity has been applied to all columns of type REAL
in the excluded.* pseudo-table of an UPSERT.
Ticket [5a3dba8104421320]
FossilOrigin-Name: 67381dadede98a55d8d9e085d021e6fa64730
Make sure OP_RealAffinity has been applied to all columns of type REAL
in the excluded.* pseudo-table of an UPSERT.
Ticket [5a3dba8104421320]
FossilOrigin-Name: 67381dadede98a55d8d9e085d021e6fa6473071978967b6302e03b28cf2245e1
show more ...
|
|
Revision tags: version-3.29.0, version-3.28.0, version-3.27.2, version-3.27.1, version-3.27.0, version-3.26.0, version-3.25.3, version-3.25.2, version-3.25.1, version-3.25.0 |
|
| #
987db767 |
| 14-Aug-2018 |
dan <[email protected]> |
Have ALTER TABLE RENAME edit column references in CREATE VIEW statements.
FossilOrigin-Name: db829dc1a2d7afa49798a2fd32d1f070185b23e513416e65d8144fda24f23b50
|
| #
84304506 |
| 14-Aug-2018 |
drh <[email protected]> |
Fix UPSERT so that it checks the target-constraint first and fires the
DO UPDATE if that constraint is violated regardless of whether or not
other constraints are in violation. This aligns SQLite be
Fix UPSERT so that it checks the target-constraint first and fires the
DO UPDATE if that constraint is violated regardless of whether or not
other constraints are in violation. This aligns SQLite behavior with
what PostgreSQL does. Fix for ticket [908f001483982c43cdb476dfb590a1a].
FossilOrigin-Name: 529fb55e3d00472f13446117527b0896827b11e870b581af7fe7cbb7392ef3cd
show more ...
|
| #
222a384a |
| 11-Jul-2018 |
drh <[email protected]> |
On an UPSERT when the order of constraint checks is rearranged, make sure
that the affinity transformations on the inserted content occur before
any of the constraint checks. Fix for ticket [79cad5e
On an UPSERT when the order of constraint checks is rearranged, make sure
that the affinity transformations on the inserted content occur before
any of the constraint checks. Fix for ticket [79cad5e4b2e219dd197242e9e5f4e].
FossilOrigin-Name: d120c45f3dc79f67afed0e44e5133569f784bc6792b15f5d79529deac2d13072
show more ...
|
|
Revision tags: version-3.24.0, version-3.23.2 |
|
| #
f49ff6ff |
| 23-Apr-2018 |
drh <[email protected]> |
Fix a problem in sqlite3ExprCompare() associated with UPSERT.
FossilOrigin-Name: 67d0b2c15299dd20bca7254ecb33e71b5eee6024e2709bfdc36f877bf2a5679f
|
| #
79636913 |
| 19-Apr-2018 |
drh <[email protected]> |
Fix the handling of "PRAGMA count_changes=ON" with UPSERT. Also improved
the implementation of count_changes in other places, without changing the
behavior.
FossilOrigin-Name: c6f71115eb933c2aee295
Fix the handling of "PRAGMA count_changes=ON" with UPSERT. Also improved
the implementation of count_changes in other places, without changing the
behavior.
FossilOrigin-Name: c6f71115eb933c2aee295bc31e5139112463c28e15a3b3ea242fd9bac168aed9
show more ...
|
| #
c8a0c90b |
| 13-Apr-2018 |
drh <[email protected]> |
Get the ON CONFLICT DO NOTHING form of upsert working by mapping it
into INSERT OR IGNORE.
FossilOrigin-Name: d07f05e98bb9ce0f9b46db159d9df161b7499d6face6a5299ecd2d00a94fb8d0
|
| #
d5af5420 |
| 13-Apr-2018 |
drh <[email protected]> |
Get the conflict-target clause parsing working correctly, with test
cases. This change involves an enhancement to sqlite3ExprCompare() which
needs to be reviewed on trunk prior to merging.
FossilOr
Get the conflict-target clause parsing working correctly, with test
cases. This change involves an enhancement to sqlite3ExprCompare() which
needs to be reviewed on trunk prior to merging.
FossilOrigin-Name: 5bf704256206f84b3db7a5d8523215604eeb218ef8db86316d1e43ecd7248d6a
show more ...
|
| #
3b45d8bf |
| 13-Apr-2018 |
drh <[email protected]> |
Improved conflict-target matching logic.
FossilOrigin-Name: 98d32ba661f4ba662b639994b74352b695d53a33bc8a498bd09b9e02f794c81e
|
| #
e9c2e772 |
| 13-Apr-2018 |
drh <[email protected]> |
Back off of the extended upsert syntax that allows multiple ON CONFLICT
clauses. The syntax now is exactly as in PostgreSQL and MySQL. Add support
for WHERE clauses on the conflict-target phrase, f
Back off of the extended upsert syntax that allows multiple ON CONFLICT
clauses. The syntax now is exactly as in PostgreSQL and MySQL. Add support
for WHERE clauses on the conflict-target phrase, for partial indexes.
FossilOrigin-Name: 2c1b1987d8de1efa8ed7e1f199710e32ff20edf8ceec570514fc63bb1ef264e0
show more ...
|
| #
788d55aa |
| 13-Apr-2018 |
drh <[email protected]> |
Begin adding upsert logic. This is an incremental check-in.
FossilOrigin-Name: 809696434097e62e8ef486c7478b5eb62c0cf1342522a5584939fade82821410
|