The scope of extensions

Hi folks,

I'm a happy creator/user of extensions (e.g. my postgresql_debversion
extension). But I'm wondering if they can be used for more than just
simple types:

- can an extension depend upon another extension? This would probably
be implicit based upon the use of an object which belonged to another
extension? (Are the META.json dependency metadata actually used at
runtime?)

- can relations just as tables, indexes, views and associated stuff
such as triggers be included as part of an extension? Are there
limits upon what may be part of an extension?

The reason for the above is that I'd very much like to be able to
version my entire application's schema using the extension mechanism
(or something based upon the ideas in the extensions mechanism). Since
SCHEMA is already taken, maybe CREATE/ALTER/DROP_APPLICATION. This
would permit easy installation and upgrade of all the objects relating
to a single application installed in the database.

Thanks,
Roger

--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800