Uploaded image for project: 'In-Portal CMS'
  1. In-Portal CMS
  2. INP-678

Revising usage of NULL columns

    XMLWordPrintable

    Details

    • Additional information:
      Hide

      To detect all places, needs to be changed unit config validator needs to altered to search for such inconsistencies. This will save time, when we need to look at each table field to detect, that it's need to be changed.

      Show
      To detect all places, needs to be changed unit config validator needs to altered to search for such inconsistencies. This will save time, when we need to look at each table field to detect, that it's need to be changed.
    • External issue ID:
      845
    • Copy Issue Key:
    • Patch Instructions:

      Patches must be submitted through Phabricator.

      Description

      I think, that we should review how we use NULL columns in system.

      For example we INT field can't have empty value unless it is NULL. VARCHAR fields can have empty value and in most cases are NOT NULL.

      What I propose is at least to convert all columns, that contain DATE and USER_ID in them to NULL. We also have ModifiedById field for topics set to 0 in database, but to -1 (root) in unit config, which will make topic always modified by "root", once it is created on front-end.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dmitry Dmitry Andrejev [Intechnic]
                Reporter:
                alex Alex
                Developer:
                Alex
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: