Put db in UTC+1 for integration tests

[tjenkinson]

Followup for #4216

I tested (zql-integration-tests) with the patch in the above PR reverted and things broke, so this adds some coverage

[vercel]

@tjenkinson is attempting to deploy a commit to the Rocicorp Team on Vercel.

A member of the Team first needs to authorize it.

[tjenkinson]

seems weird to have 2 different types for time in the same db, but maybe this is fine for testing?

Otherwise maybe it should be a new column, but then more tests would need updating

[tantaman]

Yeah, I think this is fine for the test schema since we want to try various types.

[tjenkinson]

Hmm I think the failures might be real.

Bit confused because in sql.ts createPlaceholder there's also some handling where it's plural and that's missing the AT TIME ZONE 'UTC' for the timestamp cases. Maybe it needs it?

But making that change still doesn't fix the tests

[tantaman]

Bit confused because in sql.ts createPlaceholder there's also some handling where it's plural and that's missing the AT TIME ZONE 'UTC' for the timestamp cases. Maybe it needs it?

Checking this out. Been on spring break over the last week.

[tantaman]

Some of the test failures are having too much precision from Postgres. That's not too bad.

The real worrying ones are the ones with completely different values before the decimal part.

[tantaman]

The real worrying ones are the ones with completely different values before the decimal part.

This was caused by the CVR tests not inserting with a timezone and so defaulting to the server's timezone.

44c9eda

Note to self (and @darkgnotic) cvr-store::putDesiredQuery may be incorrect if inserting a number does not also carry the timezone.

edit: looks like serializeTimestamp does the right thing by converting to toISOString which will carry the timezone.

mono/packages/zero-cache/src/types/pg.ts

Lines 48 to 71 in d042cb8

	function serializeTimestamp(val: unknown): string {
	switch (typeof val) {
	case 'string':
	return val; // Let Postgres parse it
	case 'number': {
	if (Number.isInteger(val)) {
	return new PreciseDate(val).toISOString();
	}
	// Convert floating point to bigint nanoseconds.
	const nanoseconds =
	1_000_000n * BigInt(Math.trunc(val)) +
	BigInt(Math.trunc((val % 1) * 1e6));
	return new PreciseDate(nanoseconds).toISOString();
	}
	// Note: Don't support bigint inputs until we decide what the semantics are (e.g. micros vs nanos)
	// case 'bigint':
	// return new PreciseDate(val).toISOString();
	default:
	if (val instanceof Date) {
	return val.toISOString();
	}
	}
	throw new Error(`Unsupported type "${typeof val}" for timestamp: ${val}`);
	}