Problems with Postgres column types / compatibility in Table definitions about drift

[simolus3]

Thanks for reporting all these issues! Having interchangeable table definitions is definitely the goal here.

boolean() does not work at all in Postgres as the generated CHECK constraint is not needed and throws a cast error.

You need to enable the dialect generation option for the dialects you plan on using, by default drift will only use sqlite3. It's horrible that this isn't mentioned on the postgres page, I'll fix that.

dateTime() does not work. One must use PgDateTime as follows (but this isn't documented):

What's going wrong with dateTime()? We seem to have tests for that, but perhaps they are missing something?

I tried to make some idiomatic shortcuts, but they don't work:

Yeah unfortunately those all can't work since we essentially have to look at the syntax of the table to figure out its schema, these aren't proper macros that could run at compile time.