Project

General

Profile

Feature #71

Checking for existing fields while installing/removing extras

Added by Anonymous about 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
-
Category:
-
Target version:
Start date:
June 29, 2012
Due date:
% Done:

100%

Estimated time:

Description

When installing any extra (package, plugin, etc.) verification is required if the current field already exists in the database. If the field that is going to be added is already in the database it should skip it and continue the installation. When removing any extra it shouldn't remove the field that can be used by other installed extras. Probably, an additional flag is required for the tag «field» that will point to such fields.

History

#1

Updated by Anonymous about 8 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

The feature is added.

If a field that is going to be added during extras installation already exists the script adds the extra's name to the column 'extras' of the existing field using comma («,») as a delimiter. Else it just creates a new field.
During removing any extra the script checks if more then 1 extra uses the field and remove the extra's name that is going to be removed from the field's extras list. If there is only one extra for the field it removes the field at all.

#2

Updated by Anonymous about 8 years ago

Committed revision [2196]

#3

Updated by Vasily Bezruchkin about 8 years ago

  • Subject changed from Checking for existing fields while installing/removing extras. to Checking for existing fields while installing/removing extras

Also available in: Atom PDF