On 10/7/14, 1:08 PM, Rodolfo Campero wrote:
> If it were possible to mark a function as "private for its extension" that would be awesome (the opposite would work
too,i.e. a way to specify a public API, meaning the rest is private). For big extensions it's not clear which functions
canbe used directly by users of the extension and which ones are just implementation details.
I would love to have that both for extensions as well as outside of extensions. If you're doing sophisticated things in
yourdatabase you'll end up wanting private objects, and right now the only "reasonable" way to do that is to throw them
ina _blah schema and try to further hide them with permissions games. :(
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
