Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PostgreSQL Database Modeler

pgmodeler.com.br

Post reply on HN
Print view View original

11–20 of 39 posts

Re: PostgreSQL Database Modeler

#11

Post by route66 »

mariusmg wrote: post #4
Thunderer wrote: post #2

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

I'd never understood while people code in their native language. It's just so.....wrong.

I'll help you.

Develop an application for support of financial and tax regulations for a certain country. You will have verbs and nouns which describe the situation clearly.

You develop an application from specifications written another language than English. They exist.

The biggest failure I keep seeing are futile attempts to translate concepts under these circumstances into English.

I agree in this case: when you want to invite collaboration on github, English (or Chinese?) would be better suited.

Re: PostgreSQL Database Modeler

#12

Post by ps2000 »

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…

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... ;)

Re: PostgreSQL Database Modeler

#14

Post by davyjones »

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.

My understanding is that this is not exactly a GUI client.

You can give pgXplorer (http://pgxplorer.com) a shot which is open source and the binaries are readily available. Disclaimer: I am the lead dev of pgXplorer.

Re: PostgreSQL Database Modeler

#15

Post by epo »

ps2000 wrote: post #12
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…

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.

Re: PostgreSQL Database Modeler

#16

Post by Thunderer »

route66 wrote: post #11
mariusmg wrote: post #4

Earlier quoted context omitted.

I'd never understood while people code in their native language. It's just so.....wrong.

I'll help you. Develop an application for support of financial and tax regulations for a certain country. You will have verbs and nouns which describe the situation clearly. You develop an application from specifications written another language than English. They exist. The biggest failure I keep seeing are futile attempts to translate concepts under these circumstances into English. I agree in this case: when you w…

Even in financial / tax software it is possible to create an abstraction in which you can safely write English code and move all specific terms into some i18n module. Of course if you are not clever enough to do that it's not that bad to use /required/ language, but in this case we talk about strictly technical tool for database modeling, so no excuses - it definitely needs to be translated in order to be accessible for other GitHubbers.

Re: PostgreSQL Database Modeler

#17

Post by joesb »

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…

Looks like standard disclaimer to me.

What open source project would be bold enough to say he will be responsible for all loss due to using his tool.

Re: PostgreSQL Database Modeler

#19

Post by CaptainZapp »

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.

Re: PostgreSQL Database Modeler

#20

Post by rbanffy »

joesb wrote: post #17
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…

Looks like standard disclaimer to me. What open source project would be bold enough to say he will be responsible for all loss due to using his tool.

> What open source project would be bold enough to say he will be responsible for all loss due to using his tool.

How many proprietary products would? Last time I checked a very popular one prohibited customers from even publishing their own benchmarks...

Post reply on HN