[xuwei-fit2cloud]

Filtering operation logs by time raises a timezone error on SQLModel 0.0.45 and later because its inferred datetime type requires aware parameters. Audit writers and time-range queries use naive datetimes, and migration 055 creates sys_logs.create_time as TIMESTAMP WITHOUT TIME ZONE.

Declare the existing SQLAlchemy type explicitly so filtering, log inserts, and returned timestamps retain their established behavior. This aligns ORM metadata with the existing database column; no schema or data migration is needed.

Validation:

• Reproduced the reported time-range query error and default log-insert failure on the unmodified source with SQLModel 0.0.45 and 0.0.48.
• Passed 7 local checks each on SQLModel 0.0.31, 0.0.45, and 0.0.48 (21 checks), exercising the packaged audit API routes against isolated PostgreSQL: no filter, the reported range with inclusive boundaries and millisecond exclusions, pagination, empty results, combined status filtering, Excel export, and default inserts. Returned timestamps were checked for timezone shifts.
• Compilation, diff checks, and Alembic's single-head check passed. Existing Ruff diagnostics remain: 20 UP045 warnings and a formatting discrepancy, verified on the unmodified baseline; the import-order warning was resolved.
• The route harness overrides database and translation dependencies; full browser, product authentication/license, and container deployment acceptance were not performed. Test scripts and fixtures remain local and are excluded from this PR as requested.

Reference: SQLModel datetime compatibility change.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.