| 1 | | One thing i have realised that the `bulk_create` doesn't supports `F` expressions directly, so a part of this feature would also include how to incorporate the value for the current `conflicting_row` to the value of the dictionaries which we will be passing, cause the `bulk_create` will throw the errors at the tests. There can be two ways either get the values from the db in the current dictionary of `update_fields`, and when operations are done on the python side, the batched_insert will send the data to db or After the the bulk insert has been done , a separate code shall run to update those field values which raised conflicts...... but i dont think using `update` in a `bulk_create` is a nice approach? I need your all opinions on this.. |
| | 1 | One thing i have realised that the `bulk_create` doesn't supports `F` expressions directly, so a part of this feature would also include how to incorporate the value for the current `conflicting_row` to the value of the dictionaries which we will be passing, cause the `bulk_create` will throw the errors at the tests. There can be two ways either get the values from the db in the current dictionary of `update_fields`, and when operations are done on the python side, the batched_insert will send the data to db or After the the bulk insert has been done , a separate code shall run to update those field values which raised conflicts...... but i dont think using `update` in a `bulk_create` is a nice approach? I need some opinions and advices on this.. |