| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Roman Neuhauser <neuhauser(at)sigpipe(dot)cz> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: arrays, composite types |
| Date: | 2005-09-11 16:11:39 |
| Message-ID: | 87br2z4m9w.fsf@stark.xeocode.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Roman Neuhauser <neuhauser(at)sigpipe(dot)cz> writes:
> I'm looking for an equivalent of my_composite_type[] for use as a
> parameter of a pl/pgsql function. What do people use to dodge this
> limitation?
>
> Background: I have a few plpgsql functions that basically accept an
> array of objects decomposed into arrays of the objects' attributes:
What do you want to do with these arrays? Why do you want to work with them in
plpgsql?
When you get to this point I think I would start looking at using plperl and
using Dumper to store the objects in a text column. You're trading off
database normalization against being able to express arbitrarily complex data
structures.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2005-09-11 16:42:09 | Re: Function to test for Valid Date |
| Previous Message | Alex | 2005-09-11 16:10:43 | Function to test for Valid Date |