{"categories":[{"label":"Software Development","url":"https://skillfed.io/packages/category/software-development/13"},{"label":"Front-Ends","url":"https://skillfed.io/packages/category/database-front-ends/2"}],"enrichment":{"capability":"Provides a SQLAlchemy DateTime type that consistently handles timezone-aware datetimes across database vendors, storing all values in UTC and returning aware datetime objects regardless of whether the underlying database supports native timezone types.","skillfed_tags":["timezone-handling","cross-database","abandoned-but-stable"],"use_cases":["Store event timestamps consistently across SQLite development and PostgreSQL production databases","Ensure all datetime values in a multi-database application are UTC-normalized without application-level conversion","Set server-side default timestamps using utcnow() that work identically on SQLite, MySQL, and PostgreSQL","Build timezone-aware ORM models that return aware datetime objects from all query results","Migrate applications from naive to timezone-aware datetimes while maintaining database compatibility"],"what_it_does":"SQLAlchemy-Utc solves the problem of inconsistent timezone handling across different database backends. SQLAlchemy's built-in DateTime type with timezone support works well on databases like PostgreSQL that have native timestamptz types, but fails silently on SQLite and MySQL, which lack native timezone support. This package provides a drop-in UtcDateTime replacement that normalizes behavior: it accepts only aware datetime objects, converts them to UTC before storage, and always returns aware UTC datetimes from queries, regardless of the underlying database.\n\nThe package also includes a utcnow() helper function as a server-side alternative to func.now() for setting default timestamps. It's designed for applications that need consistent, predictable datetime handling across multiple database backends without manual UTC conversion logic in application code.","worth_installing":"Yes, with conditions. The package solves a real cross-database datetime problem and has no security vulnerabilities. However, it is abandoned (last commit August 2022, no activity for nearly four years) and only explicitly supports Python up to 3.9. Install it if you need consistent UTC datetime handling across SQLite/MySQL and PostgreSQL and are willing to maintain it yourself or pin to a stable SQLAlchemy version; avoid it if you require active maintenance or support for the latest Python versions."},"id":"sqlalchemy-utc","links":{"html":"https://skillfed.io/packages/sqlalchemy-utc","md":"https://skillfed.io/packages/sqlalchemy-utc.md","pypi":"https://pypi.org/project/sqlalchemy-utc/"},"maintenance":{"status":"abandoned"},"meta":{"latest_release":"2021-09-24","license_spdx":null,"license_treatment":"permissive","name":"SQLAlchemy-Utc","python_support":"unspecified","summary":"SQLAlchemy type to store aware datetime values"},"popularity":{"monthly_downloads":197960,"position":9744,"tier":"top_15000"},"security":{"n_vulnerabilities":0},"version":"0.14.0"}