Skip to content

add support for automatic time to unix epoch integer conversion

POC related to #216 discussion.

Unfortunately, i don't see how i can do thing as clever as i wanted, there doesn't seems to be an easy way to adapt the content inserted according to the column type at the "bind" step where time.Time is converted to string.

So, there is no column type check which make integerTimeFormat and writeTimeFormat incompatible. The current code use integerTimeFormat instead of writeTimeFormat if both are provided, but we may want something more strict.

Merge request reports

Loading