Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You're right, offering a solution to MySQL problems in a thread is generally useless.

I don't really get what point the author is trying to make.

I also don't take detailed performance advice from people who can't keep a blog up. Yeah, must be the wrong backend.



How could you possibly not get the point? It's the first two (2) sentences "Considering MySQL? Use something else."


I used Postgres on a project and my main concern with it is that whatever GUIs were available were seriously lacking. Phppgadmin is awful.

If you're really pushing its capabilities then there may be better solutions than MySQL but for bog standard applications and websites there is no alternative as far as I'm concerned.


You should've used pgAdmin [1], it's much better than PhpPgAdmin [1]. I have not used the MySQL GUI (MySQL Workbench [2])that Oracle/Sun/MySQL sells with the Enterprise license but by its feature list I suspect that it provides comparable functionality to pgAdmin (which is FOSS). I would not put any of Php{Pg,My}Admin interfaces in the same category - they're too lacking IMO.

[1] http://www.pgadmin.org/

[2] http://www.mysql.com/products/workbench/


I'll second pgadmin. I finally woke up to the fact that I should start using Postgres a few months ago, and pgadmin made my initial foray into postgres very straight forward


I use MySQL and Postgres, depending on the project.

What other option is so obvious that you can't even name it?


SQLite is so obvious, and in many cases it's just enough. Or, hsqldb if you're into Java.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: