On Sat, Sep 01, 2007 at 03:03:14PM -0400, Tom Lane wrote: > Jeff Davis <[EMAIL PROTECTED]> writes: > > Can we also provide syntax which would be equivalent to setting "var" > > for the function to be whatever the current value happens to be when the > > ALTER FUNCTION is run? Possible syntax might be something like: > > > ALTER FUNCTION func(args) SET var TO CURRENT; > > Hmmm ... that's certainly do-able, though I'm not sure how much it helps > the use-case you suggest. The search path still has to be set at the > top of the module script, no?
Better one place than scores of places... > However, I like an explicit option of this sort a lot better than the > automatic version Greg was suggesting ... I'm willing to do it if people > want it. > > One problem is that we'd have to make CURRENT a reserved word to make it > work exactly like that. Can anyone think of a variant syntax that > doesn't need a new reserved word? I'm not good at the synonym game, but I did have an idea related to the SET syntax, so I'll just post it here... If you needed to set a bunch of GUCs on a function, having a load of SET statements might be a bit tedious... I'm wondering if there's some way to specify them like an array? SET {'search_path=CURRENT', 'enable_seqscan=false', ...} Or now that we have arrays of complex types, perhaps an array of type GUC... Either case would at least take care of CURRENT... -- Decibel!, aka Jim Nasby [EMAIL PROTECTED] EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
pgpg1lqt11vA1.pgp
Description: PGP signature