And FWIW from my end, an array that cannot contain null values seriously
affects the ability to utilize this tool in an application with any degree
of sophistication. As it stands now, if I have a bad value, I must
substitute a dummy value :( or null out the whole array and lose a lot of
info :(( One of the reasons we are testing the limits of postgreSQL is
because these features separate it from some of the other options. Hope to
see this fixed! Thanks for the feedback and for listening to me vent.
Kathy
At 05:58 PM 9/10/2004, Bruce Momjian wrote:
>Joe Conway wrote:
> > Bruce Momjian wrote:
> > > Kathy Smith wrote:
> > >>I understand from searching around that it is on the "To Do" list to
> allow
> > >>null values in arrays. Can anyone tell me where this is in the
> > >>implementation process and/or if there is a work around?
> > >
> > > Uh, no one is implementing it and there is no workaround. :-)
> > >
> > > If you are considering coding it, read the developers FAQ>
> > >
> >
> > FWIW, in the past I've "made noises" about implementing support for NULL
> > array elements. I couldn't find the time to do it for 8.0, but I'm
> > hopeful that I will be able to find the time to do it for 8.1. However
> > if someone else wants to have at it, don't let me get in the way ;-)
>
>OK, great.
>
>--
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania 19073
>
>---------------------------(end of broadcast)---------------------------
>TIP 7: don't forget to increase your free space map settings
