Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

db: separate tables #959

Merged
merged 1 commit into from
May 6, 2020
Merged

db: separate tables #959

merged 1 commit into from
May 6, 2020

Conversation

rerowep
Copy link
Contributor

@rerowep rerowep commented Apr 27, 2020

  • Creates for every module a separate metadata and id table in the DB.

Why are you opening this PR?

How to test?

  • Verify everything works fine and there separate metadata and id tables for each module.

Code review check list

  • Commit message template compliance.
  • Commit message without typos.
  • File names.
  • Functions names.
  • Functions docstrings.
  • Unnecessary commited files?
  • Extracted translations?

@rerowep rerowep self-assigned this Apr 27, 2020
@rerowep rerowep requested a review from BadrAly April 27, 2020 22:06
@rerowep rerowep changed the title db: separate db tables db: separate tables Apr 27, 2020
@rerowep rerowep force-pushed the wep-#1382-seperate-tables branch 3 times, most recently from 7a3f5fb to 00283e7 Compare April 28, 2020 14:57
@rerowep rerowep force-pushed the wep-#1382-seperate-tables branch from 00283e7 to 6330981 Compare May 1, 2020 12:43
@iGormilhit iGormilhit self-requested a review May 4, 2020 11:32
Copy link

@iGormilhit iGormilhit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commit message, with small corrections:

db: separate tables

* Creates for every resource a separate metadata and id table in the database.

Is it one table per resource, or two table per resource? If it's only one then simplify like this:
* Creates for every resource a separate database table.
If it two, then your proposal is ok.

And try to explain the benefit of this separation. 🙂

@rerowep rerowep force-pushed the wep-#1382-seperate-tables branch 2 times, most recently from 7993953 to f79ebc8 Compare May 5, 2020 07:41
@rerowep rerowep force-pushed the wep-#1382-seperate-tables branch from f79ebc8 to 9c1c777 Compare May 6, 2020 07:23
* Creates for every resource a separate metadata and id table in the database.
With this change export and import of one resource should be easier and
the access to seperate smaler tables are hopefully faster for big
datasets.

Co-Authored-by: Peter Weber <[email protected]>
@rerowep rerowep force-pushed the wep-#1382-seperate-tables branch from 9c1c777 to c1ec9d9 Compare May 6, 2020 12:20
Copy link

@iGormilhit iGormilhit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commit message approved.

@rerowep rerowep merged commit be5a329 into rero:dev May 6, 2020
@rerowep rerowep deleted the wep-#1382-seperate-tables branch May 7, 2020 07:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants