The normal practice to use numbers like 6100, 6101, 6102, 6200, 6201, 6202, etc...
Are there any reasons to use 1, 2, 3 for the update functions?

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Closed (works as designed)

Yes because as the comments above the update functions state, they are going to be removed once the module has reached an alpha/beta. Right now they're just there to support intra-dev-build updates. I won't need them at all once in alpha/beta.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Thanks for the reply. I was wondering about that because the other maintainer said that intra-dev updates are not supported.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

No problem. Once I was pretty confident that I had the data structure/organization pretty solid and with no more major changes, I decided to start writing intra-dev updates. At the worst now it's just adding an extra field or two, or renaming/deleting variables, which is no problem. The data structure has been changing greatly in 6.x-1.x, so that's quite a different case.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Still, inter-dev updates should be supported; differently, the users will not happy on using the development snapshot, if it requires them to uninstall the previously installed version. I can imagine the happiness of a user with 10000 nodes, when he needs to uninstall a development snapshot just to install a development snapshot of the same branch.
The reply given by a user about this said all with just a single word: ridiculous.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

I've answered the the original question and said that intra-dev updates are supported on 6.x-2.x and I don't want to argue anymore since this is not a relevant discussion to 6.x-2.x.

Anonymous’s picture

Anonymous (not verified) commented

Are there any reasons to use 1, 2, 3 for the update functions?

I would suggest that contrib modules stick to the 1, 2, 3 plan but then there is the "Drupal Way"(tm). Really the update numbers are just a sequential number that is stored in the system table for the module. The 6 (Drupal version) 1 (module version) XX (update number) was created out of an imagined sense of where the update belonged. It was thought that this nomenclature would be easier for users/developers to understand. Instead, in the developer world it has created many instances of confusion.