Opened 5 years ago

Closed 3 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: dmisev, pcampalani
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 Changed 5 years ago by dmisev

  • Owner changed from dmisev to mrusu
  • Status changed from new to assigned

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

comment:2 Changed 5 years ago by mrusu

  • Resolution set to fixed
  • Status changed from assigned to 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.

comment:3 follow-up: Changed 5 years ago by dmisev

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

comment:4 in reply to: ↑ 3 Changed 5 years ago by mrusu

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 Changed 5 years ago by dmisev

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 Changed 5 years ago by mrusu

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

comment:7 Changed 5 years ago by dmisev

  • Resolution fixed deleted
  • Status changed from closed to 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:8 follow-up: Changed 5 years ago by dmisev

Should be closed?

comment:9 in reply to: ↑ 8 Changed 5 years ago by mrusu

Replying to dmisev:

Should be closed?

Not yet, the patch is still pending

comment:10 Changed 5 years ago by pbaumann

  • Resolution set to fixed
  • Status changed from reopened to closed

comment:11 Changed 4 years ago by dmisev

  • Cc pcampalani added
  • Complexity set to Very Hard
  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:12 Changed 4 years ago by pcampalani

  • Owner changed from mrusu to pcampalani
  • Status changed from reopened to assigned

comment:13 Changed 3 years ago by pcampalani

  • Complexity changed from Very Hard to Medium

comment:14 Changed 3 years ago by pcampalani

  • Owner changed from pcampalani 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 Changed 3 years ago by pcampalani

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

comment:16 Changed 3 years ago by dmisev

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

comment:17 Changed 3 years ago by gxinghua

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

comment:18 Changed 3 years ago by pbaumann

  • Resolution set to fixed
  • Status changed from assigned to closed

indeed, it's completed.

Note: See TracTickets for help on using tickets.