Closed (works as designed)
Project:
Deadwood
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
5 Dec 2008 at 13:28 UTC
Updated:
24 Dec 2008 at 19:25 UTC
In 5.x version there was function:
/**
* Update from version 1.x to version 2.x.
*/
function resource_conflict_update_5200() {
...
after conversion function disappear.
Comments
Comment #1
solotandem commentedMy understanding of the conversion functions is that the current 5.x install hook routine should reflect the current 5.x schema included in any 5.x update hooks. The two use cases on use of the 6.x module:
1) For someone installing the 6.x module for the first time, the schema is contained in the install hook which Deadwood converts.
2) For someone who is migrating from 5.x to 6.x, then absent a schema change due solely to the migration, the schema is current.
In either case a 6.x update hook is only needed if there is a change from 5.x to 6.x and you as the module write would have to supply such a routine (labeled update_6xxx). Any 5.x update routines are not needed (as they are already reflected in the 5.x install routine which again is converted by Deadwood).
I do not see this as an issue. If I am missing something here, please let me know.
Comment #2
solotandem commentedComment #3
solotandem commented