Julien Fastré ad5e780936
Do not update the createdAt column when importing postal code which does not change
The conflict resolution clause in the SQL command of the PostalCodeBaseImporter service has been updated. It now only changes the 'updatedAt' timestamp if either the 'center' position or the 'label' actually differs from the existing entry. This ensures that the 'updatedAt' field reflects when meaningful changes occurred.
2024-07-19 13:42:48 +02:00
..
2023-06-12 18:03:39 +02:00
2023-06-18 21:44:10 +02:00
2023-06-19 21:02:19 +02:00
2023-06-26 14:27:07 +02:00
2023-06-27 18:46:04 +02:00
2023-07-07 13:21:22 +02:00
2023-07-14 13:03:29 +02:00
2023-07-15 09:00:03 +02:00
2023-07-20 12:30:51 +02:00
2023-09-14 16:17:22 +02:00
2023-09-14 17:14:46 +02:00
2023-09-18 11:54:12 +02:00
2023-09-19 09:47:33 +02:00
2023-09-27 17:09:22 +02:00
2023-10-05 09:42:42 +02:00
2023-10-17 17:39:30 +02:00
2023-10-17 23:15:56 +02:00
2023-10-24 20:52:46 +02:00
2023-10-26 15:23:01 +02:00
2023-10-26 16:07:34 +02:00
2023-10-26 17:39:55 +02:00
2023-11-05 23:50:15 +01:00
2023-11-07 13:28:11 +01:00
2023-11-07 16:18:33 +01:00
2023-11-16 11:07:34 +01:00
2023-11-16 11:07:34 +01:00
2023-11-21 14:14:11 +01:00
2023-11-24 12:39:13 +01:00
2023-11-29 22:23:42 +01:00
2023-12-11 17:23:47 +01:00
2023-12-20 11:49:38 +01:00
2024-02-08 21:21:49 +01:00
2024-02-09 00:11:11 +01:00
2024-02-21 19:49:43 +01:00
2024-03-26 18:10:18 +01:00
2024-03-26 22:10:18 +01:00
2024-04-12 12:58:23 +02:00
2024-05-14 16:05:51 +02:00
2024-06-05 16:21:11 +02:00
2024-06-05 17:08:57 +02:00
2024-06-18 10:16:39 +02:00
2024-07-01 09:53:41 +02:00
2024-07-03 12:22:53 +02:00