Am 17.10.11 10:53, schrieb Thomas Kellerer: > Susanne Ebrecht, 17.10.2011 09:31: >> Hello, >> >> I couldn't find that somebody already mentioned it. >> >> PostgreSQL isn't supporting CHAR(0). >> >> An empty string has a length of 0. >> >> CHAR(0) can have two values: NULL and empty string. >> >> In MySQL it is very common to simulate not null boolean >> by using CHAR(0). >> >> This is a little bit annoying on migration topics. > > While not move on to a cleaner approach during the migration and use a > "boolean not null"?
Sounds much too straight forward, not mysql-ish artistic enough... Regards, Andreas -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
