My best suggestion offhand is to create a plpgsql function that returns text
and make it loop through the array and output in the format that you're used
to. Then change you select statements from:
"select a,b,c from mytable;"
to:
"select a,myfunction(b),c from mytable;"
where b is the varchar array attribute.
I don't think that was the answer you were looking for, but it's the best I
could think of right now.
It can be very troublesome to deal with upgrades when changes like that aren't
mentioned in the migration notes.
Regards,
Jeff
On Friday 13 September 2002 01:47 pm, Glen Eustace wrote:
> Hi,
>
> last night we upgraded our primary web server, which included upgrading
> postgres to 7.2.1
>
> A rather unexpected change in behaviour has broken one of our
> applications.
>
> We have a column containing a varchar array. This used to be displayed
> with all the elements quoted, seperated by commas i.e.
> { "a","b","c","d" }
>
> Now, the quotes are only present if the element includes a quote or a
> space. i.e.
> { a,"b b",c,d }
>
> This is much more difficult to parse and will involve lots of code
> changes in our application. Is there ANY setting I can change that will
> result in the data being displayed as before.
