Big values for `timestamptz` are convert to `null`

[BierDav]

In my database I used +infinity as a value in my postgres database:

But on powersync-js and powersync-kotlin (on KMP) the value received is not a big date as expected, but null

Error in streamingSync: Error code: 1299, message: powersync_control: replacing into review_day, id = 2, data = {"id":2,"ordinal":2147483647,"parent_id":2,"period_end_exclusive":null,"period_start_inclusive":"2029-01-02T23:00:00.000000Z","type":1}: internal SQLite call returned CONSTRAINT_NOTNULL: NOT NULL constraint failed: review_day.period_end_exclusive

After some testing it seems like 9999-01-01 00:00:00.000000 +00:00 is the maximum value that persist their value to the client db.

[rkistner]

That does sound like a bug - according to our docs, infinity should become 9999-12-31 23:59:59Z.

Two questions:

1. Are you using timestamp or timestamptz for this column in Postgres?
2. Are you using config.edition: 2 or config.timestamps_iso8601: true in your sync rules file?

[BierDav]

1. I use timestamptz
2. Yes: config.edition: 2

[rkistner]

I tested this but couldn't reproduce the issue. This is what I get with config.edition: 2:

Postgres	SQLite
infinity	9999-12-31T23:59:59.000000Z
-infinity	9999-12-31T23:59:59.000000Z
19999-12-31	null

This matches expected behavior.

If you get something different, could you please test using our sync diagnostics client? That would isolate any service issues from potential client/app issues.

[BierDav]

Ok so I guess that I have to ensure that Jetbrains/Exposed - the ORM - uses the infinity keyword instead of the real Max Value of Kotlin LocalDateTime.

EDIT: I can't read, sorry for that 😂🙈