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 Dimitar Misev, 12 years ago

Owner: changed from Dimitar Misev to mrusu
Status: newassigned

Mihaela, don't forget to close when you submit the script to the repo.

comment:2 by mrusu, 12 years ago

Resolution: fixed
Status: assignedclosed

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.

comment:3 by Dimitar Misev, 12 years ago

Shouldn't the Makefile be modified to substitute the @sysconfdir@ in the script?

in reply to:  3 comment:4 by mrusu, 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 Dimitar Misev, 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:6 by mrusu, 12 years ago

Tested and updated the wiki page. Now it is a simple .sh file.

comment:7 by Dimitar Misev, 12 years ago

Resolution: fixed
Status: closedreopened

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:8 by Dimitar Misev, 11 years ago

Should be closed?

in reply to:  8 comment:9 by mrusu, 11 years ago

Replying to dmisev:

Should be closed?

Not yet, the patch is still pending

comment:10 by Peter Baumann, 11 years ago

Resolution: fixed
Status: reopenedclosed

comment:11 by Dimitar Misev, 11 years ago

Cc: Piero Campalani added
Complexity: Very Hard
Resolution: fixed
Status: closedreopened

comment:12 by Piero Campalani, 10 years ago

Owner: changed from mrusu to Piero Campalani
Status: reopenedassigned

comment:13 by Piero Campalani, 10 years ago

Complexity: Very HardMedium

comment:14 by Piero Campalani, 10 years ago

Owner: changed from Piero Campalani to gxinghua

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 Piero Campalani, 10 years ago

PS Meanwhile also PetascopeDevGuide has been heavily updated (+ UML diagram).

comment:16 by Dimitar Misev, 10 years ago

I think this will be a good ticket for Xinghua, to familiarize with the petascope database.

comment:17 by gxinghua, 10 years ago

Add update15.sql in changeset:7413988. Should this ticket be closed?

comment:18 by Peter Baumann, 10 years ago

Resolution: fixed
Status: assignedclosed

indeed, it's completed.

Note: See TracTickets for help on using tickets.