Ticket #78 (closed enhancement: fixed)

Opened 3 years ago

Last modified 1 year ago

DG update optimization

Reported by: flack Assigned to: piotras
Priority: major Milestone: 1.8 Thor
Component: Midgard Core Version:
Keywords: Cc:

Description

Running Datagard -> update takes 10-15 minutes on a 46MB database.

Since you have to run this so often (when updating between Midgard versions, when installing a new component or when changing the schema XML of an already installed component), it can cause unpleasant amounts of downtime for the server (since it is recommended to stop Apache before doing the update).

So I was wondering if it would be possible to optimize this a bit. For example, is it really necessary to update all metadata columns and GUIDs in all tables when I just install one new component or update from 1.8.2 to 1.8.3?

Change History

02/11/08 13:52:08 changed by piotras

  • status changed from new to closed.
  • resolution set to fixed.

(In [14845]) Added default FALSE is_linked member to type property struct. Removed some unused key and indexes and added colname_idx convention to have as many indexes as needed. Fix #193 Fix #214 Fix #78 Ported some database related routines from 1-9 branch

09/30/08 14:57:17 changed by bergie

  • milestone set to 1.8 Thor.