Bug? When editing a row, the timestamp defaults to 12:30PM of today, which throws an error. Moving the date to sometime in the future makes it work, but obviously the created_at time shouldn't change on an edit. Not sure how it's possible to not touch it at all? This is just using the standard timestamp column as suggested by default.

Hello @gorbypark! This thread has been automatically created from your message in #843999948717555735 a few seconds ago. We have already mentioned the @User so that they can see your message and help you as soon as possible! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ``...`` menu) and select "Leave Thread" to unsubscribe from future updates. Want to change the title? Use the ``/title`` command! We have solved your problem? Click the button below to archive it.

Editing a row with standard created_at with now default and changing another column works fine on my instance. Must be more to it.

ah, it appears to be just Safari. Looks/works normal in Chrome.

Thread was archived by @gorbypark. Anyone can send a message to unarchive it.