Process in code when experiencing an install error in a custom module

Jeff Greenberg <[email protected]> Sat, 6 Oct 2012 20:28:30 -0400
Newsgroups gmane.comp.php.drupal.devel
Message-ID <CAPpCgRakdSpKq2iFX616tg1izFuX5m0zJFSuSHa18j8_DswJwQ@mail.gmail.com>
I'm curious what others are building into their module install process in
the event of an error partway through. For example, if your install script
creates one or more bundles, fields and field instances, if an error occurs
at some point during that process, do you handle it all like a transaction
and back out what you have created to that point?

My instinct would be to do that, though I realize it can get complicated,
such as the event where some of the fields that were to be created earlier
on in the process already existed, etc. I'm asking, though, because of the
several modules I've looked at so far, none seem to be doing this.

Jeff
---
drupal.org/user/367108
linkedin.com/in/jeffrgreenberg
accidentalcoder.com / ayendesigns.com
@accidentalcoder