Multiple patches and propery table changes
Posted 12 August 2003 - 18:06
I create the patches without error. When I apply patch 1, the PatchName property is added to the database as expected. When I apply patch 2 to a fresh install, the PatchName property is added to the database as exected. When I apply patch 1 followed by patch 2, the PatchName property stays at the value used in patch 1--it does NOT get update with the new value.
Why will additional patches not update the property added by another patch? Could this be because the property does not exist in the original database? There shouldn't be any restrictions on patches overwriting the same property, should there?
Thanks for any info,
Posted 12 August 2003 - 19:53
Posted 12 August 2003 - 20:11
As this is a small update, the version stays the same. I can't make one patch supersede another, because they are independent fixes. I can't make each patch "know about" all other other patches, because it's impossible to know about future fixes, and the patches should be able to be installed in any order.
I'm really up against a wall here. This would seem to be a serious deficiency in WI, and it also appears to be one that they are finally addressing in WI 3.0--when they add the ability to sequence patches. This seems to imply that there is no sequencing in the current implementation, which compromises the ability to change the database with multiple small update patches.
Posted 12 August 2003 - 20:22
What you could try (just an idea) is a custom action that would set the property. If both patches have such an action, but patch 2 has it later in the sequence, it should win. (Alternatively it could append to the existing property so you get a list of all installed patches)
Posted 12 August 2003 - 20:48
Thanks for the reply and the idea: I couldn't set the property for each patch, as I can't depend on the order of patch installation by the customer, but appending to the property might just work. I suspect I'll have to add a CA for each patch, each with a difference sequence number, but in the end I can have a property which contains all applied patches, which is really what I want anyway. I'll report back success or failure.
Posted 15 August 2003 - 22:31