Re: [GENERAL] Oddity in column specifications for table creation

2007-12-11 Thread Tom Lane
Marc Munro <[EMAIL PROTECTED]> writes: > This works fine: > "str2"varchar(40) > This does not: > "str2""pg_catalog"."varchar"(40) Yeah. That's because in all existing PG releases, type modifiers are handled by hard-wired grammar productions that *only* work

Re: [GENERAL] Oddity in column specifications for table creation

2007-12-11 Thread Marc Munro
On Tue, 2007-11-12 at 19:32 -0500, Tom Lane wrote: > Marc Munro <[EMAIL PROTECTED]> writes: > > This works fine: > > "str2"varchar(40) > > This does not: > > "str2""pg_catalog"."varchar"(40) > > Yeah. That's because in all existing PG releases, type modifie