"Brendan Jurd" <direvus(at)gmail(dot)com> writes:
> The patch is very invasive (at least compared to any of my previous
> patches), but so far I haven't managed to find any broken behaviour.
I'm sorry to suggest anything at this point, but... would it be less invasive
if instead of requiring the immediate cast you created a special case in the
array code to allow a placeholder object for "empty array of unknown type".
The only operation which would be allowed on it would be to cast it to some
specific array type.
That way things like
UPDATE foo SET col = array;
INSERT INTO foo (col) VALUES (array);
could be allowed if they could be contrived to introduce an assignment cast.
Ask me about EnterpriseDB's RemoteDBA services!
In response to
pgsql-hackers by date
|Next:||From: Tatsuo Ishii||Date: 2007-11-30 10:15:35|
|Subject: Re: PostGreSQL and recursive queries...|
|Previous:||From: Usama Dar||Date: 2007-11-30 10:08:02|
|Subject: Re: Release Note Changes|
pgsql-patches by date
|Next:||From: Alvaro Herrera||Date: 2007-11-30 12:21:17|
|Subject: Re: pg_regress: paths in largeobject test|
|Previous:||From: Simon Riggs||Date: 2007-11-30 09:54:19|
|Subject: Re: [PATCHES] Partition: use triggers instead of rules|
pgsql-general by date
|Next:||From: Madison Kelly||Date: 2007-11-30 10:22:34|
|Subject: Moving lock file (/tmp/.s.PGSQL.<port>)|
|Previous:||From: Martijn van Oosterhout||Date: 2007-11-30 10:07:35|
|Subject: Re: invalid byte sequence for encoding "UTF8"|