Jack Christensen

>> The current implementation treats nil as SQL NULL > Actually, it treats nil as JSON null (See my tests). By `nil` I meant the untyped `nil` as opposed to...

You can use `OptionAfterConnect()` to get inject custom code into the new connection path with database/sql / stdlib. You could register your new data type there.

I don't know. As far as I can tell that should work. It might be necessary to step through the debugger to find out what's going wrong.

So I just had a chance to look closer at this. Do I understand correctly that this 64xid patch actually changes the data type and binary format of a fixed...

> @jackc yes, this patch changes the data type and binary format of XID. But not for OID. This was done in order to increase the transaction counter to avoid...

> If this patch is included in the core, we will use only uint64 for xid. Any given server will only have one type, but pgx would be expected to...

@nurlantulemisov It might be possible, I'm not sure, but there are definitely a few complications. A custom type doesn't have to support the binary format. The query sending code would...

It's on purpose in the general case for pgtype. That is, types only can assign to string if they are a string-like type. It may be worth revisiting that decision...

> The problem is Z; time.Parse does not recognize Z as a valid timezone specifier and so falls back to parsing as UTC. It ends up in UTC, but it...

I'm not sure how gorm works. But the following reads an `pgtype.Inet` with `database/sql`: ```go package main import ( "database/sql" "fmt" "log" "github.com/jackc/pgtype" _ "github.com/jackc/pgx/v4/stdlib" ) func main() { db,...