On Mon, 20 Mar 2006 22:01:23 +1200 Christopher Sawtell <[EMAIL PROTECTED]> wrote:
> On Friday 17 March 2006 11:21, Nick Rout wrote: > > On Thu, 16 Mar 2006 17:32:04 +1300 > > > > Christopher Sawtell wrote: > > > On Thursday 16 March 2006 16:04, Roy Britten wrote: > > > > On Thu, 2006-03-16 at 15:54 +1300, Don Gould wrote: > > > > > Is there any kind of gui tools that > > > > > you know of for postgres? > > > > > > > > pgAdmin III http://www.pgadmin.org/ > > > > > > Also you could use the sql:// protocol in Konqueror. > > > > > > imho using these click and point gui tools is a somewhat hazardous > > > exercise, because they don't, as a general rule, conveniently save a > > > .sql source code file from which you can rebuild the database from > > > scratch. > > > > Yes but at any stage you can dump the database generating scripts - wel > > you can in mysql, I assume you can in postgresql too. > Yes you can do that in PostgreSQL, but you then lose all and every syllable > of documentation you have put in the sql source code file. I may be a > traditionalist, but I recon that if you are trying to build a project or > product which has a life, rather than a quick fix for some immediate > problem, then it's essential to have source code that's understandable and > usable by other people. > > -- > CS No, the documentation is in your schema design, and no matter what anyone says, the best tool for that design is the Mk.1 brain. You can support it with no end of ERD tools and data dictionaries, but the initial step doesn't come from there. Database dumps are for a last resort of backup (and every decent rdbms has a better option), and are not a design tool... you can't design with mysqladmin - even a fag packet is better (: Keep your schema and data separate and you'll never lose any documentation ( even MySQL supports this ). After all, data never needs comment, as there's never any accounting for folk! My $0.02, Steve
