Richard Huxton writes:
> To prevent quoting insanity, I recommend the ARRAY[] constructor rather
> than array literals. You do need the explicit typecasts.
By the same token, you might want to use ROW() rather than
composite-type literal syntax for the array elements.
> Oh - and version 8.3 or h
2009/10/24 Andrew Hall :
> Thanks Bruce,
>
> what I was looking for was the postgreSQL equivalent of table-valued
> parameters from SQL Server 2008
> (http://technet.microsoft.com/en-us/library/bb510489.aspx) or tables of
> Oracle Objects from Oracle. (Or something that would allow me to achieve
>
Andrew Hall wrote:
> Hi,
>
> I was wondering whether anybody would be able to advise me on how (if it is
> possible) to port some functionality from Oracle?
>
> This is just an example - in Oracle, I am able to do the following
>
> --
> -- Create a data type which replicates the data structure
Thanks Bruce,
what I was looking for was the postgreSQL equivalent of table-valued parameters
from SQL Server 2008 (http://technet.microsoft.com/en-us/library/bb510489.aspx)
or tables of Oracle Objects from Oracle. (Or something that would allow me to
achieve the same effect).
The example th
Tom Lane a écrit :
> Denis BUCHER writes:
>> To do this it will be a little complicated because of table
>> dependencies... And it could bug again at the next DROP COLUMN... Is
>> there a way to change my function (RETURN SETOF part) to specify the
>> column names/types ?
>
> No, not really. You
