Use timestamp with time zone for timestamp fields in projection_versions

[datafoo]

Fixes #20.

[gaslit]

May I know the status regarding this PR? Many thanks.

[dvic]

Not sure what the status of this PR is, but isn't it a better approach to have the migrations shipped (with versions) with the library? Like Oban does for example, e.g., Oban.Migrations.up(version: 11)?

[cdegroot]

@datafoo are you still interested in this change? If so, I think that @dvic is on the money here, we really should then have some (simple) versioning to run this a bit more transparently than "copy/paste this SQL". But given the minor impact of the change and the somewhat large amount of work involved, maybe not worth the trouble?

(sorry for the late response, we had a maintainer change and a large backlog of work)

[datafoo]

I am still interested, I believe we should use the most appropriate data type. And yes it would be great if we could avoid to run manual SQL statements.