jayvynl
jayvynl
> Looks like it's hardcoded to 'UTC' This is intentional, to be consistent with the behavior of postgresql backend.
Anyway, do you really need to set timezone in database level? The recommended way to deal with timezone is using `django.utils.timezone` module.
sorry no plan, currently define table out of Django and use unmanaged model.
released as v1.4
Sorry for the late review. Could you add any unit test for this function?
> Hi, I've update my PR with unittest Could you please fix the CI code lint error?
See #49 History models are rarely used and I don't have much time diving into the relatively complicated Django migration system. So this is not planned.
Nice job.
Yes, it's intentional. Think of this situation. There is a cluster of two node A and node B. A Model of MergeTree engine is defined as: ```python class Student(models.ClickhouseModel): name...