12 Commits

Author	SHA1	Message	Date
demoManito	b2ff96b2e2	fix	2023-10-20 20:54:41 +08:00
demoManito	685ece80d4	fix test	2023-10-20 20:48:53 +08:00
demoManito	e9c3b25552	fix: SQL `UPDATE SET` is missing spaces	2023-10-20 20:36:26 +08:00
Jinzhu	e1b4c066a8	Fix FullSaveAssociations, close #4874	2021-11-29 11:02:44 +08:00
Jinzhu	649d02fddd	Add batch upsert tests	2020-06-09 09:04:32 +08:00
Jinzhu	aaf0725771	Refactor for performance	2020-06-08 17:21:26 +08:00
Douglas Danger Manley	72d0fa6196	Fix Statement Where clone array corruption in v2 ... Method-chaining in gorm is predicated on a `Clause`'s `MergeClause` method ensuring that the two clauses are disconnected in terms of pointers (at least in the Wherec case). However, the original Where implementation used `append`, which only returns a new instance if the backing array needs to be resized. In some cases, this is true. Practically, go doubles the size of the slice once it gets full, so the following slice `append` calls would result in a new slice: * 0 -> 1 * 1 -> 2 * 2 -> 4 * 4 -> 8 * and so on. So, when the number of "where" conditions was 0, 1, 2, or 4, method-chaining would work as expected. However, when it was 3, 5, 6, or 7, modifying the copy would modify the original. This also updates the "order by", "group by" and "set" clauses.	2020-06-07 16:54:01 -04:00
Jinzhu	82d55b1054	Add OnConflict DoUpdates test	2020-06-07 12:50:00 +08:00
Jinzhu	52b763aab3	Add convert map Assignments helper	2020-06-06 17:47:30 +08:00
Jinzhu	7b6b9c4d22	Add tests for Columns	2020-05-31 00:42:52 +08:00
Jinzhu	504f42760a	Refactor clause Writer	2020-03-09 17:07:00 +08:00
Jinzhu	1f38ec4410	Finish clauses tests	2020-02-08 23:23:45 +08:00