Ticket #4438 (new Feature Requests)

Opened 3 years ago

Last modified 2 years ago

database consistency check

Reported by: john@erba.tv Assigned to:
Priority: minor Milestone: Undetermined
Component: Core - Module Admin Version: 2.8-branch
Keywords: db consistency check Cc:
Confirmation: Need Feedback Distro:
Backend Engine: Asterisk 1.6 Distro Ver:
Backend Ver: 1.6.2 SVN Revision (if applicable):

Description

It would be useful if each module exposed a db_consistency_check function so that it would be possible to continue to give warnings (via the notifications on status page) of db inconsistencies. Each module should be able to define what is considered inconsistent by running a set of queries on it's own or other modules' tables.

The consistency check could be run in a similar way to existing notifications checks which notifies of invalid extensions, upgrades etc.

Change History

07/15/10 10:58:38 changed by p_lindheimer

  • confirmation changed from Unreviewed to Need Feedback.

can you provide some examples of the types of issues you have run into that would help here? There are some places that consistency checks are already run, such as retrieve_conf runs a consistency check for things like duplicate extensions and destination problems which require looking at everyone to determine.

07/15/10 14:22:22 changed by john@erba.tv

I was thinking of - check that the tables have the right structure (columns, keys) as per the latest installed schema (like today I found an extra column I should not have had anymore) - check that foreign keys are valid - check that columns that require mandatory entries are filled. ...

01/23/11 20:00:45 changed by p_lindheimer

  • milestone changed from 2.9 to 2.10.

deferring at least one release. First steps would be for someone to define some sort of standard, or maybe it's simply tied into the logging mechanism and run at retrieve_conf time. In any event, once we get a standard to go by, we can look at starting to add this to modules since it's a feature that does not have to be done all at once.

09/17/11 20:59:49 changed by mbrevda

  • milestone changed from 2.10 to Undetermined.