Opened 12 years ago
Closed 10 years ago
#212 closed task (fixed)
Graphical database schema for petascope
Reported by: | mrusu | Owned by: | gxinghua |
---|---|---|---|
Priority: | minor | Milestone: | 8.4 |
Component: | petascope | Version: | 8.3 |
Keywords: | Cc: | Dimitar Misev, Piero Campalani | |
Complexity: | Medium |
Description
Currently there is no graphical representation of the petascope database schema, so it would help to have one. A command line tool is preferred, as it can be integrated with the update script. The image should be added to the petascope documentation page http://rasdaman.eecs.jacobs-university.de/trac/rasdaman/wiki/PetascopeDevGuide
Suggestion: SchemaSpy http://schemaspy.sourceforge.net/
Change History (18)
comment:1 by , 12 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Both the script and the generated schema have been added to http://rasdaman.eecs.jacobs-university.de/trac/rasdaman/wiki/PetascopeDevGuide, since the script does not belong to petascope deployment, but is rather part of the development process.
follow-up: 4 comment:3 by , 12 years ago
Shouldn't the Makefile be modified to substitute the @sysconfdir@ in the script?
comment:4 by , 12 years ago
Replying to dmisev:
Shouldn't the Makefile be modified to substitute the @sysconfdir@ in the script?
Yes. but this can be easily done when generating a new schema when the db is updated, which doesn't happen very often.
comment:5 by , 12 years ago
Ok please document how it should be modified, or even better, just make the path to the settings file another argument to the script and remove the .in from the name?
comment:7 by , 12 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Great! Do you think it's possible to add some description of the tables to the generated schema documentation? The -desc or -meta options in SchemaSpy could be potentially useful for this.
comment:9 by , 12 years ago
comment:10 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
comment:11 by , 11 years ago
Cc: | added |
---|---|
Complexity: | → Very Hard |
Resolution: | fixed |
Status: | closed → reopened |
Would be nice to document the new petascope schema in this way, what do you think Piero?
http://www.craigkerstiens.com/2013/07/29/documenting-your-postgres-database/
http://www.craigkerstiens.com/2013/08/02/use-dollar-quoting-anywhere/
comment:12 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | reopened → assigned |
comment:13 by , 11 years ago
Complexity: | Very Hard → Medium |
---|
comment:14 by , 10 years ago
Owner: | changed from | to
---|
Using COMMENT ON statements is indeed very cool, Dimitar.
A new updateX.sql
file could be created for this: this can simply be a copy-pasting activitiy from files in browser:applications/petascope/src/main/db/petascope/update8, especially schema.sql
.
comment:15 by , 10 years ago
PS Meanwhile also PetascopeDevGuide has been heavily updated (+ UML diagram).
comment:16 by , 10 years ago
I think this will be a good ticket for Xinghua, to familiarize with the petascope database.
Mihaela, don't forget to close when you submit the script to the repo.