-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jobs-table-schema #36
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@code-akki please give your feedback on whether it's OK to use triggers for updates.
According to me, It's not great if one table is using it and the rest aren't. Either all tables need to use it, or none.
@gopal-mahajan @ThorodanBrom Yes we can remove the triggers as of now and add it later on as a separate migration as and when required. |
Sure i will remove the triggers for now. Yes @code-akki we need the created_at and updated_at as it is required for the job status api response. |
No description provided.