"Chuck McDevitt" <[EMAIL PROTECTED]> writes: > Just a curiosity question: Why is the type of a literal '1' "unknown" > instead of varchar(1)?
Even if it was assigned a text datatype it would be the unconstrainted "text" not varchar(1). If we used varchar(1) then things like: create table foo as select 'foo'; would create a table with varchar(3) which would then complain if you tried to insert 'foobar' into. There doesn't seem to be enough evidence that the user intended to constrain the input to just 'foo' in that case. Of course right now you get a table with a column of type "unknown" which is very unlikely to be what the user expects. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
