You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "Zzih96 (via GitHub)" <gi...@apache.org> on 2024/02/01 08:31:07 UTC

Re: [I] [Bug] [API&MASTER] 3.2.0 The restart of MySQL 5.7 can cause an Auto Increment ID reset, potentially resulting in the inability to execute command. [dolphinscheduler]

Zzih96 commented on issue #15543:
URL: https://github.com/apache/dolphinscheduler/issues/15543#issuecomment-1920765825

   > I think add a code field would be better
   
   I noticed that the `job_id` field in the `t_ds_trigger_relation` table also holds the `id` field from the `t_ds_process_instance` table. If I add a `code` field to the `t_ds_command` table, should I also add a `code` field to the `t_ds_process_instance` table for association? This change may have significant implications, so I believe it warrants further discussion.
   <img width="762" alt="image" src="https://github.com/apache/dolphinscheduler/assets/158246610/e9c8c802-7d7e-4678-9961-e10f96bd54eb">
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org