Based on this post https://www.timescale.com/blog/getting-sensor-data-into-timescaledb-via-django/, it seems that creating a TimescaleDB hypertable in Django is straightforward by using RunSQL in a migration file and not defining it in the model. Has anyone tried this and identified any potential caveats?
#adding timescale through runSQL
rapid isle
green whale
Hello! I've used Timescale with Django in the way you describe, with unmanaged models and SQL migrations. It worked fine 😄 The one caveat we had was that our hypertables had composite primary keys, think (timestamp, some_id) which is a feature that was not supported in Django at the time so we had to define just the timestamp as the PK in the model, kind of "lying" to django.
One of my teammates at the time actually gave a talk about this at DjangoCon US so I'll share the link https://www.youtube.com/watch?v=hXctK2NQTsc
Also of note, composite primary keys are coming to Django soon! there's a PR in progress for it https://github.com/django/django/pull/18056
