On Dec15, 2010, at 21:28 , Dimitri Fontaine wrote: > Florian Pflug <fgp@phlo.org> writes: >> Not if CREATE EXTENSION allows you install hstore into an arbitrary schema. > > It also allows you to change it after the fact, and to easily track it > down. Here's an updated version of the query to find the hstore type OID > reliably once we have extensions in: >
> <snipped SQL> That's certainly cool, but having to use different methods to find a type depending on how it has been installed isn't exactly ideal. And not every user-defined type will be installed via CREATE EXTENSION.
Thus I still believe something like a type identifier that is independent from it's name and schema would be nice to have.
In case you wonder if than means every object should have such a handle - they should *not*. What makes types special is that they are used on the protocol level, not only on the SQL level. Thus, handling them frequently falls into the real of client libraries, not individual client applications, making it more important to be able to handle them in an application-agnostic way.
Right! In particular this is one reason why I believe that hstore should be built-in type.
