4 ms·

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

by motter 14y ago

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 of this tool." https://github.com/pgmodeler/pgmodeler#warning https://github.com/pgmodeler/pgmodeler#warning

joesb 14y ago
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.
- rbanffy 14y ago
  > 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...
CaptainZapp 14y ago
Frankly, Even with tools costing thousands of Euros it would be incredible stupid to export models, or generated code into production environment.
- mgummelt 14y ago
  Why?
  - jacques_chester 14y ago
    Some data is more valuable than kitten photos and chat logs.
    - mgummelt 14y ago
      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.
      - jacques_chester 14y ago
        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.
ps2000 14y ago
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... ;)
- epo 14y ago
  DbVisualizer (http://www.dbvis.com/ 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.
  - ExpiredLink 14y ago
    > Doesn't have many design tools (well not any really, Someone posted a link to a modelling tool.
- jpdoctor 14y ago
  > The only code I would trust is the code I generate myself... ;) I dunno about you, but it's pretty clear that the code I generate myself is the last code I would trust.
- ericcholis 14y ago
  HeidiSQL [1] is pretty good for most tasks. Although, it doesn't have an easy GUI for building databases. [1] http://www.heidisql.com http://www.heidisql.com
  - ExpiredLink 14y ago
    Neither pgAdmin nor Heidi are modelling tools.
    - ericcholis 14y ago

by motter 14y ago

joesb 14y ago

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.

rbanffy 14y ago
> 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...

CaptainZapp 14y ago

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

mgummelt 14y ago
Why?
- jacques_chester 14y ago
  Some data is more valuable than kitten photos and chat logs.
  - mgummelt 14y ago
    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.
    - jacques_chester 14y ago
      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.

ps2000 14y ago

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

epo 14y ago
DbVisualizer (http://www.dbvis.com/ 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.
- ExpiredLink 14y ago
  > Doesn't have many design tools (well not any really, Someone posted a link to a modelling tool.
jpdoctor 14y ago
> The only code I would trust is the code I generate myself... ;) I dunno about you, but it's pretty clear that the code I generate myself is the last code I would trust.
ericcholis 14y ago
HeidiSQL [1] is pretty good for most tasks. Although, it doesn't have an easy GUI for building databases. [1] http://www.heidisql.com http://www.heidisql.com
- ExpiredLink 14y ago
  Neither pgAdmin nor Heidi are modelling tools.
  - ericcholis 14y ago