On Sat, Feb 12, 2011 at 6:32 AM, Nikhil S <[email protected]> wrote: > >> > Hmmm, well variables can default to NULL too. The backend code tries to >> > track those variables which default to NULL or to other values. For the >> > rest, it defaults them to "". It then uses construct_md_array to >> > generate >> > the output string for type TEXTOID. Dunno if we can have nothing (an >> > empty >> > string) as valid TEXTOID output. I guess it's a limitation for this >> > type. >> > Let me see if we can do something here on the backend side... >> >> Doesn't really help, as we need to ensure it works sanely with >> existing servers too. >> > > Well it will work with only those servers which support default values for > arguments (PG 8.4 onwards, right?). > > But I guess you mean, we should find a solution more on the pgadmin side > instead of tinkering with the backend?
Yes. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgadmin-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
