Spaces:
Paused
Paused
fix: use naive UTC datetime in stats endpoint for PostgreSQL compatibility
Browse filesThe created_at column stores naive UTC datetimes, but the week_ago
comparison used timezone-aware datetime causing PostgreSQL type mismatch.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
outlook2api/admin_routes.py
CHANGED
|
@@ -91,10 +91,9 @@ async def admin_stats(
|
|
| 91 |
):
|
| 92 |
_verify_admin(request)
|
| 93 |
stats = await get_stats(db)
|
| 94 |
-
# Recent accounts (last 7 days)
|
| 95 |
-
week_ago = datetime.now(timezone.utc).replace(hour=0, minute=0, second=0)
|
| 96 |
from datetime import timedelta
|
| 97 |
-
week_ago =
|
| 98 |
recent = (await db.execute(
|
| 99 |
select(func.count(Account.id)).where(Account.created_at >= week_ago)
|
| 100 |
)).scalar() or 0
|
|
|
|
| 91 |
):
|
| 92 |
_verify_admin(request)
|
| 93 |
stats = await get_stats(db)
|
| 94 |
+
# Recent accounts (last 7 days) — use naive UTC to match column type
|
|
|
|
| 95 |
from datetime import timedelta
|
| 96 |
+
week_ago = datetime.utcnow().replace(hour=0, minute=0, second=0) - timedelta(days=7)
|
| 97 |
recent = (await db.execute(
|
| 98 |
select(func.count(Account.id)).where(Account.created_at >= week_ago)
|
| 99 |
)).scalar() or 0
|