2023-05-10 12:20:57.747 CEST [6404] LOG:  le système de bases de données a été arrêté à 2023-05-07 14:24:08 CEST
2023-05-10 12:20:57.801 CEST [5944] LOG:  le système de bases de données est prêt pour accepter les connexions
2023-05-20 12:33:52.289 CEST [4888] ERREUR:  la valeur d'une clÃ© dupliquÃ©e rompt la contrainte unique Â« res_users_login_key Â»
2023-05-20 12:33:52.289 CEST [4888] DÃ‰TAIL:  La clÃ© Â« (login)=(anass.inadam@gmail.com) Â» existe dÃ©jÃ .
2023-05-20 12:33:52.289 CEST [4888] INSTRUCTION :  INSERT INTO "res_users" ("id", "action_id", "active", "company_id", "create_date", "create_uid", "login", "notification_type", "odoobot_failed", "odoobot_state", "partner_id", "signature", "write_date", "write_uid") VALUES (nextval('res_users_id_seq'), NULL, true, 1, '2023-05-20 10:33:52.184453', 4, 'anass.inadam@gmail.com', 'email', false, NULL, 8, '', '2023-05-20 10:33:52.184453', 4) RETURNING id
2023-05-20 13:17:02.687 CEST [3204] ERREUR:  la valeur d'une clÃ© dupliquÃ©e rompt la contrainte unique Â« hr_employee_user_uniq Â»
2023-05-20 13:17:02.687 CEST [3204] DÃ‰TAIL:  La clÃ© Â« (user_id, company_id)=(2, 1) Â» existe dÃ©jÃ .
2023-05-20 13:17:02.687 CEST [3204] INSTRUCTION :  UPDATE "hr_employee" SET "user_id"=2,"work_email"='anass.inadam@gmail.com',"write_date"='2023-05-20 11:17:02.665483',"write_uid"=2 WHERE id IN (2)
2023-05-20 13:17:06.902 CEST [6944] ERREUR:  la valeur d'une clÃ© dupliquÃ©e rompt la contrainte unique Â« hr_employee_user_uniq Â»
2023-05-20 13:17:06.902 CEST [6944] DÃ‰TAIL:  La clÃ© Â« (user_id, company_id)=(2, 1) Â» existe dÃ©jÃ .
2023-05-20 13:17:06.902 CEST [6944] INSTRUCTION :  UPDATE "hr_employee" SET "user_id"=2,"work_email"='anass.inadam@gmail.com',"write_date"='2023-05-20 11:17:06.878057',"write_uid"=2 WHERE id IN (2)
