Repository navigation
Use AwareDateTime when generating field from DateTime(timezone=True) #407
Description
I didn't investigate this. I don't know if there would be an issue with this.
Basically, when I have a model with
creation_date = sqla.Column(sqla.DateTime(timezone=True), nullable=False)I need to override the auto field in the schema
class ItemSchema(AutoSchema):
class Meta:
model = Item
id = msa.auto_field(dump_only=True)
creation_date = ma.fields.AwareDateTime(required=True)I suppose this could be automatized.
Activity
lafrech commentedon Oct 3, 2026
While we're at it, should we also use
NaiveDateTimein other cases?DYNOSuprovo commentedon Oct 4, 2026
Regarding using \NaiveDateTime\ when \ imezone=False\ (or omitted):
While symmetrical with \AwareDateTime\ for \ imezone=True, defaulting to \NaiveDateTime\ for standard \DateTime\ could be a breaking change for existing users who deserialize ISO 8601 strings with timezone offsets into standard columns (where marshmallow's default \ ields.DateTime\ previously permitted it).
One gentle approach could be:
Happy to adapt PR #741 if the team prefers adding \NaiveDateTime\ mapping as well!