ER diagram

(Keith Brown) #1

Is there an ER diagram floating about anywhere that I'm missing?


K

(Avi Miller) #2

(Must. Avoid. Making. Bad. Medical. Joke.)

Not that I'm aware of, but Greg would know for sure.
(Greg Sherwood) #3

Nope. You could generate one from the source but you'd need a pretty big wall to put it on.

(Keith Brown) #4

yeah was trying that (big printer is a bigger ask! ;-) - do you recommend a tool to do it? 2 I've tried so far seem to miss the relationships... (I will get the marker pen out but....)
(Greg Sherwood) #5

Sorry, but no.

(Avi Miller) #6

What have you tried so far, out of interest? I've never tried to build one myself. :)
(Aleks Bochniak) #7

Have you used Case Studio?

(Keith Brown) #8

don't think so - when I get to work tomorrow I'll check. But having has a look at the raw 'pg_dump -s' there doesn't seem to be any FKs set (y/n?) which explains the absence of relationships in the diagrams… tbh first postgres DB i've dealt with. Oracle /MSSQL/MySQL experience so may be doing something wrong…

(Avi Miller) #9

Correct – we don't have any foreign keys in the database (either in PostgreSQL or Oracle).

(Greg Sherwood) #10

We cant use foreign keys in the DB because we have IDs of shadow assets (LDAP users, groups etc) that don't exist in the sq_ast table. So we need to do all the integrity work in the code rather than the DB. We use DB transactions to ensure we don't lose data half way through a change.

(Keith Brown) #11

this was the last one I tried:

http://microolap.com/products/database/postgresql-designer/download/

Works as expected I guess... does get all the tables and draws them out (but without FKs no relationships). I'll get busy with the marker pen ;-)

Cheers
(Avi Miller) #12

It is fairly straight-forward to work out the implied relationships.