You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MySQL supports the syntax DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP nowadays which is very useful for updated_at fields. I would try to add such support myself but looking at the code it doesn't seem very easy to do so at first glance.
I'm currently only using this package for it's schema diff functionality for a declarative schema approach that can be used with any framework and ORM (mainly for Laravel) or even just vanilla PHP. As such being able to define updated_at fields like this ensures that this functionality will always work regardless of how the row gets updated.
If any more information is needed do not hesitate to ask!
PS, I haven't been able to find anything to support virtual columns, are these unsupported and should I create another feature request for this?
The text was updated successfully, but these errors were encountered:
Feature Request
Summary
MySQL supports the syntax
DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
nowadays which is very useful forupdated_at
fields. I would try to add such support myself but looking at the code it doesn't seem very easy to do so at first glance.I'm currently only using this package for it's schema diff functionality for a declarative schema approach that can be used with any framework and ORM (mainly for Laravel) or even just vanilla PHP. As such being able to define
updated_at
fields like this ensures that this functionality will always work regardless of how the row gets updated.If any more information is needed do not hesitate to ask!
PS, I haven't been able to find anything to support virtual columns, are these unsupported and should I create another feature request for this?
The text was updated successfully, but these errors were encountered: