I'm from Romania. Coding in your native language is likely used as a safeguard....it means it will be very hard to outsource the product :) .
Coding in your native language on a OSS project is even worse.
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.
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.
"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."
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.
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.
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.
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.
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.
38 comments
[ 2.3 ms ] story [ 114 ms ] threadDevelop 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.
But for Open Source projects coding in English is probably the best way to attract contributors.
Will update here later with an English fork.
"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
The only code I would trust is the code I generate myself... ;)
Someone posted a link to a modelling tool.
I dunno about you, but it's pretty clear that the code I generate myself is the last code I would trust.
[1] http://www.heidisql.com
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...
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.
No, I don't count 'not looking native' as a problem.
http://stuconnolly.com/blog/sequel-pro-postgresql-support/