PostgreSQL Database Modeler • Hacker News Board

Re: PostgreSQL Database Modeler

#31

Post by ExpiredLink » Thu, Sep 27, 2012, 5:55 PM UTC

epo wrote: post #15

ps2000 wrote: post #12

Earlier quoted context omitted.

After all there aren't many high quality opensource RDBMS GUIs available. The only one I know is pgAdmin and even pgAdmin has some serious bugs. (GUI freezes easily when you have many windows open and/or do large queries; import/export barely work) The only code I would trust is the code I generate myself... ;)

DbVisualizer ( http://www.dbvis.com/ ) is an excellent cross-platform, multi-product GUI tool. Doesn't have many design tools (well not any really, but neither does PgAdmin). Java-based and not free, which gives freeloaders and snobs something to complain about. No relationship, just someone who has been happy to be a customer for many years.

> Doesn't have many design tools (well not any really,

Someone posted a link to a modelling tool.

Re: PostgreSQL Database Modeler

#32

Post by nathancahill » Thu, Sep 27, 2012, 5:57 PM UTC

garindra wrote: post #6

For the people that have already tried it, is this finally a good Postgres client for the MacOSX? Haven't found any that comes close to Sequel Pro for MySQL.

I've had a good experience with Tuple: http://www.tuplesapp.com/

Re: PostgreSQL Database Modeler

#33

Post by rcamera » Thu, Sep 27, 2012, 6:00 PM UTC

Thunderer wrote: post #2

All READMEs in English, all code in Portuguese? Really?

I might fork it later tonight and translate both code and comments to English. Might be an interesting experience...

Will update here later with an English fork.

Re: PostgreSQL Database Modeler

#34

Post by nealabq » Thu, Sep 27, 2012, 6:17 PM UTC

lzm wrote: post #21

Thunderer wrote: post #2

All READMEs in English, all code in Portuguese? Really?

Most people don't speak English in Brazil, or do so very poorly.

Same situation in the USA.

Re: PostgreSQL Database Modeler

#35

Post by dmishe » Thu, Sep 27, 2012, 8:10 PM UTC

artiom wrote: post #13

garindra wrote: post #6

For the people that have already tried it, is this finally a good Postgres client for the MacOSX? Haven't found any that comes close to Sequel Pro for MySQL.

its not Sequel Pro but you can try http://inductionapp.com

It's a great app, but for different purpose. Induction is mainly for viewing/analyzing _data_, where pgAdmin, while horrible looking, is for managing database schema.

Re: PostgreSQL Database Modeler

#36

Post by mgummelt » Thu, Sep 27, 2012, 9:56 PM UTC

CaptainZapp wrote: post #19

motter wrote: post #5

Note the warning from the README: "Although this is a major upgrade version of pgModeler it is recommended NOT EXPORT the models created directly to production environments. Not all possible code generation were tested in this way, is its your own risk export the models into environments that are not intended for testing. The project's author is not responsible for any possible loss of data due the inappropriate use…

Frankly, Even with tools costing thousands of Euros it would be incredible stupid to export models, or generated code into production environment.

Why?

Re: PostgreSQL Database Modeler

#37

Post by jacques_chester » Fri, Sep 28, 2012, 2:07 AM UTC

mgummelt wrote: post #36

CaptainZapp wrote: post #19

Earlier quoted context omitted.

Frankly, Even with tools costing thousands of Euros it would be incredible stupid to export models, or generated code into production environment.

Why?

Some data is more valuable than kitten photos and chat logs.

Re: PostgreSQL Database Modeler

#38

Post by mgummelt » Fri, Sep 28, 2012, 3:44 AM UTC

jacques_chester wrote: post #37

mgummelt wrote: post #36

Earlier quoted context omitted.

Why?

Some data is more valuable than kitten photos and chat logs.

So I shouldn't use a compiler? A bug in generated app code could corrupt my kitten photos just as easily as generated DB models could.

Re: PostgreSQL Database Modeler

#39

Post by jacques_chester » Fri, Sep 28, 2012, 3:45 AM UTC

mgummelt wrote: post #38

jacques_chester wrote: post #37

Earlier quoted context omitted.

Some data is more valuable than kitten photos and chat logs.

So I shouldn't use a compiler? A bug in generated app code could corrupt my kitten photos just as easily as generated DB models could.

The point here is not "don't use tools". It's "test your changes". Pushing straight from a tool into production, or making the change by hand in production, or anything on the spectrum inbetween, is unwise.