You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
column.is_nullable is always a string, YES or NO (ie. the datatype yes_or_no), so !!column.is_nullable will always be true.
This can (probably) be fixed by adding c.is_nullable = 'YES' as is_nullable, to the select. It may however conflict with the c.*, which in my opinion should be replaced by the actual columns used for clarity.
Tested on PostgreSQL 13.9 (Debian 13.9-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
The text was updated successfully, but these errors were encountered:
On this line:
sequelize-typescript-generator/src/dialects/DialectPostgres.ts
Line 306 in 6e2238d
column.is_nullable
is always a string,YES
orNO
(ie. the datatypeyes_or_no
), so!!column.is_nullable
will always be true.This can (probably) be fixed by adding
c.is_nullable = 'YES' as is_nullable,
to the select. It may however conflict with thec.*
, which in my opinion should be replaced by the actual columns used for clarity.Tested on
PostgreSQL 13.9 (Debian 13.9-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
The text was updated successfully, but these errors were encountered: