Re: Array constructor requires one argument

From: David Fetter <david(at)fetter(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Joe Conway <mail(at)joeconway(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Postgresql General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Array constructor requires one argument
Date: 2007-01-09 22:13:02
Message-ID: 20070109221302.GO25475@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jan 09, 2007 at 04:09:21PM -0500, Tom Lane wrote:
> Joe Conway <mail(at)joeconway(dot)com> writes:
> > Unless we can convince ourselves that array-of-UNKNOWN is not dangerous,
> > I don't think this is easily solved.
>
> One possibility that might handle Martijn's problem is to allow the
> construct
>
> ARRAY[]::type[]
>
> that is, you can have an empty ARRAY construct only if you immediately
> cast it to a specific array type. The application typically knows what
> type the data is anyway, and if it just always plasters on the cast then
> the syntax would work regardless of whether there are any elements or not.

+1 for doing it this way :)

Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter

Remember to vote!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Kroeger 2007-01-09 22:16:02 Re: ERROR: invalid memory alloc request size, and others
Previous Message Jonathan Hedstrom 2007-01-09 22:12:17 Re: ERROR: invalid memory alloc request size, and others