-
Notifications
You must be signed in to change notification settings - Fork 25
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
db: separate tables #959
Conversation
7a3f5fb
to
00283e7
Compare
00283e7
to
6330981
Compare
There was a problem hiding this 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. 🙂
7993953
to
f79ebc8
Compare
f79ebc8
to
9c1c777
Compare
* 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]>
9c1c777
to
c1ec9d9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commit message approved.
Why are you opening this PR?
How to test?
Code review check list