Skip to content

Fixing relative paths on schema and database

Gerson Esquivel Garciarequested to merge
rel_paths into lang_server_proc_upgrade

Prerequisites Checklist

Self-review checklist:

  • My code follows the style guidelines and software coding standards for this project.
  • I have performed a self-review of my code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have added appropriate tests that prove my fix/feature is effective.
  • If the source branch will not be used after this MR, I have set it to be deleted upon merging.

Documentation checklist:

  • I have checked the README and updated it if necessary.
  • I have checked the tutorial and made any documenation or results updates if necessary.
  • I have updated the CHANGELOG.

Does this MR relate to a specific issue? If so, link the issue.

No

Description of Changes

Merge request !311 (merged) includes a comment regarding that recent changes to the schema had broadened the context of some constraints by changing relative paths to absolute paths. The work on this merge request now consists of returning relative paths to reduce the scope of all established constraints. Changes were made to the database, and then the database was auto-generated.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected or break backwards compatibility)

Additional Information

@lefebvre @orl Could any of you review this MR to make sure it seems correct? I used Rob's script to fix most of the paths, and then manually modified the rest that I thought needed to be relative. I tested it using Workbench and these additions seem to raise validation errors appropriately.

Merge request reports