Re: [SQL] array_lower /array_prepend doubt
Tom Lane wrote: > Joe Conway <[EMAIL PROTECTED]> writes: > > We may need another extension to the array literal syntax in > > order to deal with this. I'll report back after I've had some time to > > study it. > > There already is support in array_in for specification of the array > dimensions (though it may be suffering bit rot for lack of use/testing). > I think the main thing needed is some thought about when array_out > should print dimensions; we don't want it doing so all the time, for > both clutter and backwards compatibility reasons. Maybe "whenever any > lower bound is not 1" would do; or maybe we want to invent a GUC switch > to control its behavior. Is this a TODO? -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (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
[SQL] passing new/old record in pl/pgsql trigger functions to other functions
Hi, In Postgresql version 7.4.1 How does one pass new/old record in a pl/pgsql trigger function to other functions? I tried to pass it directly but the select/perform statement caused an error saying "NEW used in query that is not in a rule". I've tried 'rename' in the declare block but that didn't work at all (I get 'invalid column', which I assume it means rename did not work at all). Besides copying the record columns one by one, is there any other way to do this? -- basic ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [SQL] passing new/old record in pl/pgsql trigger functions to other functions
basic <[EMAIL PROTECTED]> writes: >In Postgresql version 7.4.1 How does one pass new/old record in a > pl/pgsql trigger function to other functions? You can't ... NEW and OLD are of unspecified-record types, and there's no support for passing such things to other functions. You pretty much have to do the tedious "myfunc(NEW.f1, NEW.f2, ...)". I've done some work recently to improve the support for passing record types around as full-fledged datatypes. The above still doesn't quite work, and I can't promise that it'll get done for 7.5, but hopefully by the release after that it will. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
