crate/cratedb-django

Support `TimeField`

Open

#53 opened on Dec 24, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Python (4 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (6 stars)
PR merge metrics
 (PR metrics pending)

Description

CrateDB does not support storage for timetz, all times have to be stored either in a timestamp or timestamptz.

TimeField only takes the time part of a timestamp, CrateDB trips if we try to do:

TimeField(datetime.datetime.now().time().isoformat())
# SQLParseException[Cannot cast value `22:43:10.001021` to type `timestamp without time zone`]

Because CrateDB needs the full timestmap.

But if we pass a timestamp, the validator of the field trips with: django.core.exceptions.ValidationError: ['“2020-01-01T22:43:10.001021” value has an invalid format. It must be in HH:MM[:ss[.uuuuuu]] format.']

To fix this we should modify the validator of cratedb.fields.TimeField

Contributor guide

Research direction
Examine the current TimeField validator in cratedb/fields.py and modify it to accept time strings without requiring a full timestamp.
Tech stack
python
Domain
backenddatabase
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonDjango
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80