zulip

Author	SHA1	Message	Date
Alex Vandiver	7988aad159	user_message: Use INSERT ... ON CONFLICT for historical UM creation. Rather than use a bulk insert via Django, use the faster `bulk_insert_all_ums` that we already have. This also adds a `ON CONFLICT` clause, to make the insert resilient to race conditions. There are currently two callsites, with different desired `ON CONFLICT` behaviours: - For `notify_reaction_update`, if the `UserMessage` had already been created, we would have done nothing to change it. - For `do_update_message_flags`, we would have ensured a specific bit was (un)set. Extend `create_historical_user_messages` and `bulk_insert_all_ums` to support `ON CONFLICT (...) UPDATE SET flags = ...`.	2024-03-26 10:52:37 -07:00
Alex Vandiver	52e3c8e1b2	user_message: Move create_historical_user_messages to zerver.lib.user_message. It is not even used in zerver.actions.create_user.	2024-03-26 10:52:37 -07:00
Alex Vandiver	f15e006873	message_edit: Perform cross join in SQL, not Python. The database can do this faster than we can, and it reduces the amount of information transmitted over the wire.	2024-03-19 18:22:24 -04:00
Alex Vandiver	7ce6095003	message_edit: Handle previous subscribers and private-history streams.	2024-03-19 18:22:24 -04:00
Anders Kaseorg	05195c02c1	actions: Split out zerver.lib.user_message. Signed-off-by: Anders Kaseorg <anders@zulip.com>	2022-04-14 17:14:30 -07:00