Budget warehouse minor issues

[Ghislain Hachey]

As discussed:

• Add call to exec warehouse.logVersion (though I think by calling warehouse.buildBudgets you will get that one no!?)
• Add a call to warehouse.BuildBudgets from warehouse.buildWarehouse
• Make sure to clean the budget tables before proceeding in buildBudgets

‌

[Brian Lewis]

Add call to exec warehouse.logVersion (though I think by calling warehouse.buildBudgets you will get that one no!?)

‌

My preference has been to add a call to warehouse.logVersion at the end of each component stored procedure. This ensures that the the latest data will be always downloaded by the clients. It means that when you do a full warehouse.BuildWarehouse, the version is logged many times, but this doesn;t really matter - the final call will provide the Id for everything in that warehouse version.

Also worth observing that if you run a component on its own, e.g. warehouse.BuildBudgets , then you will force a reload of any warehouse data in the client, even though that data may not have changed.

[Brian Lewis]

task(warehouse): BuildBudgets incorporated into BuildWarehouse

Resolves #914

→ <<cset b5c23b9a8b29>>