>>>>> "Tom" == Tom Lane <t...@sss.pgh.pa.us> writes:
Tom> I think the way most people are envisioning this is that a Tom> module is a set of SQL objects (functions, types, tables, Tom> whatever). Whether any of those are C functions in one or more Tom> underlying .so files is not really particularly relevant to the Tom> module mechanism. Tom> It should be possible to have a module that doesn't contain any Tom> C code, Yes. Tom> so the concept of a defining function does not look good to me. Tom> A defining SQL script is the way to go. But I disagree with this, for the simple reason that we don't have anything like enough flexibility in the form of conditional DDL or error handling, when working in pure SQL without any procedural help. This is especially true when you start to look at how to handle conflicts, upgrades and versioning. -- Andrew. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
