On Thu, Feb 03, 2005 at 06:59:55PM -0700, Michael Fuhr wrote: > On Thu, Feb 03, 2005 at 06:44:55PM -0600, Karl Denninger wrote: > > > > As it happens, there's an "untsearch2.sql" script in the contrib directory. > > That reminds me: it would be useful if all contributed modules had > an unmodule.sql file. That would simplify reloading the module if > the definitions changed, as recently happened when STRICT was added > to functions in chkpass and a few other modules; it would also make > it easy to remove the module from a particular database if it were > no longer needed. Or is there already a way of doing this that > doesn't require you to figure out the DROP statements yourself? > Running "gmake uninstall" in the module's source directory only > removes the .so, .sql, and other installed files -- it doesn't DROP > any objects that have been created in databases. No, there is no good way to do that. What's worse, is that if it goes into the template directory, it "pollutes" every database on the system from that point forward, so you have to back it out of each in turn.... I agree with this - what would be even better would be a way to create 'subclasses' for things like this, which could then be 'included' easily. I don't know if the latter is possible - I haven't seen an obvious way to do that, but there may be a way..... -- -- Karl Denninger (karl@xxxxxxxxxxxxx) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.com Musings Of A Sentient Mind ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@xxxxxxxxxxxxxx
