special access restrictions. If you cannot call the population services the
table never contains any data. The actual table structure itself (field
definitions, keys) matters not at all and has no security issues associated
with it.
Ian Lewis (www.mstarlabs.com)
SQL, this feature applies to all functions not
> only external one
>
I will look at this in more detail, but, on first reading, I do not quite
see how it helps.
Ian Lewis (www.mstarlabs.com)
Our current report editor has no way to define a report from a
> table that does not exist in some schema somewhere, and I am not even sure
> it is possible to get it to call a procedure before attempting to access
> the schema.
>
> This may be a big problem for us. But, I do not see any obvious work
> around for it under PostgreSQL.
>
> Ian Lewis (www.mstarlabs.com)
>
do not see is how we get multiple server-side functions to
manipulate the same temporary table.
Is there a conventional means to do something like this in PostgreSQL? If
so, is there documentation somewhere on how to manage access to temporary
tables across function calls from the client?
Ian Lewis
