OpenUpgrade Server

[doc] why -u all instead of -u my_module?

Asked by Dimitri John Ledkov (ex-credativ)

It's not clear from the docs why i should be doing -u all instead of -u my_module when designing upgrade for my_module only?

Ideally I don't want to see all the xml_ids which have been done by dependencies (I'm assuming that dependencies are already properly migrated). Hence I only want to do with stuff introduced by my_module in the old & new version.

Or am I wrong somewhere?

Question information

Language:
English Edit question
Status:
Answered
For:
OpenUpgrade Server Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said : 		#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Stefan Rijnhart (Opener) (stefan-opener) said : 		#2

Hi Dmitrijs,

Dreadfully sorry, we missed a number of questions on the project because we had not configured the Launchpad answer contact timely.

The reason for propagating an '-u all' is that this allows the algorithm to detect if a model or a model's field has been moved to a different module in simple cases. If that does not apply to your setup then you should be able to update a single module. Usability wise, the refactored way of building the analysis database layout changes using interface wizards allows storing the changes per module, right into the module's migrations' subdirectory, releaving the developer from the burden of sorting out the changes that apply to a specific module. It also does not incorrectly list XML id's with a different module prefix under the prefixed module anymore, but under the module that it is actually defined in.

Cheers,
Stefan.

Revision history for this message
Stefan Rijnhart (Opener) (stefan-opener) said : 		#3

Setting state to Answered.

Can you help with this problem?

Provide an answer of your own, or ask Dimitri John Ledkov (ex-credativ) for more information if necessary.

To post a message you must log in.