Re: information_schema vs temp tables (was Re: [HACKERS] [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase `s`)

2006-09-18 Thread Greg Sabino Mullane
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tom Lane wrote: > I've done the above and now withdraw my complaints about this patch. Excellent, thank you. > I notice however that the patch seems to have touched only about half a > dozen of the information_schema views ... shouldn't more of the

Re: information_schema vs temp tables (was Re: [HACKERS] [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase `s`)

2006-09-14 Thread Tom Lane
I wrote: > If you're really intent on making it work this way, my vote is to > expose namespace.c's isOtherTempNamespace() as a SQL-callable function, > and add a test on that to the info-schema views, rather than relying on > is_visible or explicit knowledge of the temp-schema naming convention.

information_schema vs temp tables (was Re: [HACKERS] [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase `s`)

2006-09-13 Thread Tom Lane
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes: > ... I can't think of a use case where a user would not want to > append a "is_visible" clause to the query above. That or start > tracking which pg_temp_ schema belongs to whom. Well, I'm still having a problem with this, because it seems like a