The goal here is to make the behavior more explicit and also to avoid a configuration-dependent failure I observed in production, where server_default can be applied too late to satisfy a NOT NULL constraint:

sqlalchemy.exc.IntegrityError: (sqlalchemy.dialects.postgresql.asyncpg.IntegrityError) <class 'asyncpg.exceptions.NotNullViolationError'>: null value in column "time_created" of relation "sessions" violates not-null constraint

Checklist

• Add a Changelog entry
• Add the ticket number which this PR closes to the comment section