"created_at timestamp NOT NULL" The field is not generated correctly for type "time.Time"

[1514599514]

Version

1.29.0

What happened?

The mysql driver is converted normally.
Found this issue only on pgsql.

Relevant log output

Database schema

CREATE TABLE users(
  id         BIGSERIAL PRIMARY KEY,
  username   text      NOT NULL UNIQUE,
  password   text      NOT NULL,
  created_at timestamp NOT NULL DEFAULT NOW()
);

SQL queries

Configuration

Playground URL

https://play.sqlc.dev/p/ade9f663d29b7e6545cccfdc9a2e6f4f322d3c71b8ebfb6e98c46e2c0f0c5d1c

What operating system are you using?

Windows

What database engines are you using?

PostgreSQL

What type of code are you generating?

Go

[ororsatti]

You need to specify it in the override section:

https://play.sqlc.dev/p/a87f82b332688b926cb8f972dff1cc2c8b59855e95f3755c1c3d37be00cdf3f4

...
        "overrides": [
        	{
            	"db_type": "pg_catalog.timestamp",
                "go_type": "time.Time",
             }
        ]
....

More info: https://docs.sqlc.dev/en/latest/howto/overrides.html

[1514599514]

You need to specify it in the override section:

https://play.sqlc.dev/p/a87f82b332688b926cb8f972dff1cc2c8b59855e95f3755c1c3d37be00cdf3f4

...
"overrides": [
{
"db_type": "pg_catalog.timestamp",
"go_type": "time.Time",
}
]
....
More info: https://docs.sqlc.dev/en/latest/howto/overrides.html

Thank you for your solution
If there are no other considerations, I hope that SQLC can achieve consistent behavior between pgSQL and MySQL

[ororsatti]

You need to specify it in the override section:
https://play.sqlc.dev/p/a87f82b332688b926cb8f972dff1cc2c8b59855e95f3755c1c3d37be00cdf3f4
...
"overrides": [
{
"db_type": "pg_catalog.timestamp",
"go_type": "time.Time",
}
]
....
More info: https://docs.sqlc.dev/en/latest/howto/overrides.html

Thank you for your solution If there are no other considerations, I hope that SQLC can achieve consistent behavior between pgSQL and MySQL

Without getting into details, I think its harder than we thing to have consistent APIs for different databases.
That's why configuration is key - it defines consistency.

Any way hope it helps!