>
> On Tue, 2 June 1998, at 22:19:01, Bruce Momjian wrote:
>
> > > they don't always work, in the case of a table with an attribute that
> > > calls a function for its default value.
>
> > This is a good point, and something worth thinking about. Maybe we
> > could scan through the defaults for a table, and call the dumpfunction
> > command for any functions. Then when they are later attempted to be
> > created, they would fail, or we could somehow mark them as already
> > dumped.
>
> Would we look at the binary plan (aiee!) or just try and parse the
> string value 'pg_attdef.adsrc` for a function call?
I see pg_attrdef.adsrc now. Wow, that looks tough. Could we grab any
identifier before an open paren?
There has to be an easy fix for this. Can't think of it though.
--
Bruce Momjian | 830 Blythe Avenue
maillist@candle.pha.pa.us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)