litellm - 💡(How to fix) Fix tool_registry_writer: batch_upsert_tools passes text to timestamp column via .isoformat() [1 participants]

ERROR: column "created_at" is of type timestamp without time zone but expression is of type text

TL;DR

Remove the .isoformat() call when generating the now variable to allow Prisma's raw query engine to handle the datetime object conversion to timestamp natively.

Guidance

• Identify all occurrences of datetime.now(timezone.utc).isoformat() in the codebase, particularly in tool_registry_writer.py, and remove the .isoformat() call to pass the datetime object directly.
• Verify that the created_at and updated_at columns in the PostgreSQL database are of type timestamp without time zone to ensure compatibility with Prisma's native datetime to timestamp conversion.
• Review the Prisma schema to confirm that the created_at field is defined with the @default(now()) directive, ensuring that the current timestamp is used when inserting new records.
• Test the updated code to confirm that the error log lines related to the column "created_at" is of type timestamp without time zone but expression is of type text error have decreased significantly.

Example

now = datetime.now(timezone.utc)  # Remove .isoformat()
await prisma_client.db.execute_raw(
    'INSERT INTO "LiteLLM_ToolTable" '
    "(tool_id, tool_name, origin, call_policy, call_count, created_by, updated_by, key_hash, team_id, key_alias, created_at, updated_at) "
    "VALUES ($7, $1, $2, 'untrusted', 1, $3, $3, $4, $5, $6, $8, $8) "
    "ON CONFLICT ...",
    ..., now,
)

Notes

This fix assumes that the Prisma version being used supports native datetime to timestamp conversion. If issues persist, verify the Prisma version and consult the relevant documentation.

Recommendation

Apply the workaround by removing the .isoformat() call and passing the datetime object directly, as this allows Prisma's raw query engine to handle the conversion natively and resolves the error.