Related T1527
Details
- Reviewers
vlorentz zack - Group Reviewers
Reviewers - Commits
- rDSTOC2ead4ce360ba: Added comments for all tables and columns
rDSTO2ead4ce360ba: Added comments for all tables and columns
Diff Detail
- Repository
- rDSTO Storage manager
- Branch
- sql-table-column-comments
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 6300 Build 8721: tox-on-jenkins Jenkins Build 8720: arc lint + arc unit
Event Timeline
Build is green
See https://jenkins.softwareheritage.org/job/DSTO/job/tox/483/ for more details.
sha1_git is not "Git id of sha1 checksum", it's the hash of the content as a git object (ie. with the header used by git to identify blobs).
Could you also add comments on these tables, and use is instead of IS?
swh/storage/sql/30-swh-schema.sql | ||
---|---|---|
62 | Not "file creation", but the first time we saw that content. | |
64 | It's not an identifier of the "file content", just of the content | |
82–84 | I don't think comments on these columns are relevant. Maybe just one of the type. | |
113 | Same | |
140 | This comment should go into more details |
swh/storage/sql/30-swh-schema.sql | ||
---|---|---|
57–64 | the style of these could be improved to be less awkward, e.g., "length of file content" -> "file content length" also, please check our glossary, as it will give hints of how to make this both shorter and clearer, e.g., it's not "file content", it's just "content" | |
141–142 | these are incorrect, you should just refer to the general notions of "standard output / standard error", the intended reader will know what they mean |
swh/storage/sql/30-swh-schema.sql | ||
---|---|---|
57–64 | I prefer using active voice for comments. But the comments will become repetitive like,
|
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DSTO/job/tox/492/
See console output for more information: https://jenkins.softwareheritage.org/job/DSTO/job/tox/492/console
sql/upgrades/137.sql | ||
---|---|---|
87 | The db fields do not give information to add comments. Can you give some information about what is being stored. Specially fields like date offset. | |
106 | Not sure what to write here. Is is the complete revision history of a software origin? | |
134 | What to add here for date offset. | |
152 | Is there a better comment than "Primary key" for this field. | |
154 | The dev comment says
Does this comment convey the meaning? |
@twitu please use imperative form while writing commit messages. Also, do keep in mind the why-not-how when writing the body of the commit message.
- Add comments to few columns in dbversion, task and task_run
- Change double quoted comments to single quoted comments
Build is green
See https://jenkins.softwareheritage.org/job/DSCH/job/tox/270/ for more details.
- Added comments to tables dbversion, content, skipped_content and fetch_history
- Added comments for all tables and columns
- Converted double quote comments to single quote comments
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DSTO/job/tox/494/
See console output for more information: https://jenkins.softwareheritage.org/job/DSTO/job/tox/494/console
fyi, the error is:
---------------------------- Captured stderr setup ----------------------------- psql:/home/jenkins/workspace/DSTO/tox/swh/storage/sql/30-swh-schema.sql:110: NOTICE: identifier "Content blobs observed but not ingested in Software heritage archive" will be truncated to "Content blobs observed but not ingested in Software heritage a" psql:/home/jenkins/workspace/DSTO/tox/swh/storage/sql/30-swh-schema.sql:110: ERROR: syntax error at or near ""Content blobs observed but not ingested in Software heritage archive"" LINE 1: comment on table skipped_content is "Content blobs observed ... ^
The comments are not complete. I will fix the syntax issue in the next commit along with the missing comments. I am not sure what comments to add for the revision table.
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DSTO/job/tox/499/
See console output for more information: https://jenkins.softwareheritage.org/job/DSTO/job/tox/499/console
Build is green
See https://jenkins.softwareheritage.org/job/DSTO/job/tox/500/ for more details.
swh/storage/sql/30-swh-schema.sql | ||
---|---|---|
82–84 | No point deleting them now. |
Build is green
See https://jenkins.softwareheritage.org/job/DSTO/job/tox/501/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DSTO/job/tox/502/ for more details.
Almost there !
(and thanks a lot for your persistence on this one)
sql/upgrades/137.sql | ||
---|---|---|
11 | SQL (uppercase) there are a few other instances of this below, please fix all of them | |
swh/storage/sql/30-swh-schema.sql | ||
85 | URL (uppercase) | |
110 | We can leave "software heritage" implicit, given the context. How about "Content blobs observed, but not ingested in the archive" here? | |
144 | I don't think my previous comment on these fields have actually been addressed. My proposal is something like "standard output of the fetch operation" / "standard error of the fetch operation". |
Build is green
See https://jenkins.softwareheritage.org/job/DSTO/job/tox/506/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DSTO/job/tox/507/ for more details.