ot if it requires module-specific logic to convert data to a new format, or migrate old records to a new schema. Seriously, we just got the _install() and _update_x() hooks in place and they're working really well. The last thing we need is a completely different mechanism for updating being shoved into place, driven by a mess of 'intelligent' code that assumes it knows best. ;)
 
--Jeff
-----Original Message-----
From: John Pulles [mailto:john.pulles@gmail.com]
Sent: Thursday, May 11, 2006 4:17 PM
To: development@drupal.org
Subject: Re: [development] Extend database abstraction layer,to include table creation.

2006/5/11, Jeff Eaton <jeff@viapositiva.net>:
The're useful when the structure of a table evolves over time -- for example, version 1.45 of module foo adds an index for better performance. YOu can change the original definition, but you'll need these additional functions to write the update_x() function.

Probably a 'diff' can be made to determine the difference between the current tables (if they are present) and the updated definition. The install/update system would then process the differences.