I'm mulling over the possibility of a database switch for some of the projects that I have. Currently I use MySQL because the price is attractive. Unfortunatly I find that, and it's command line interface being wonderfull compared to sqlplus, being almost the only thing going for it :)
Well that's a little harsh, since I do like MySQL, but when I put it up along side Oracle (Since I also admin and program on an oracle server at another place I work with) MySQL pails in comparison.
I mean we just recently got transactions (in MySQL). We are still waiting on subselects (yes I know the latest gamma has it but if your thinking about running that in production then you are braver than I). Stored Procedures and Triggers are quite far off. Views (and maybe even materialized views) are somewhere in there just can't remember when. I just keep wanting something more from my database.
So I guess after 4 paragraphs of fluff this brings me to the real point of this message. What I would like is Oracle on a MySQL budget :)
Now there is Postgresql. I have used it a little in the past but I didn't really like it. Though that was about 4 years ago now, and I didn't use it long enough to form a solid opinion. It has the MySQL budget and it also has many of the features that Oracle has. Does anyone out there have any experiance with Postgres? If so what are your oppinions.
Also as I see it there is Oracle (I'd love to have it), MySQL (I can affored it), Postgres (Flirting with it), MS SQL (Doesn't run on Linux so I don't want to know it), and SyBase (No Idea). Are there others that I'm missing? Something else to look at? Something better to look at?
Sorry for the runon post. I just want to get some input from my fellow coders/sql'ers/admins out there on their experiances with different DBMS'.
daisho.
I've flirted with all of the above mentioned and really only stuck to the 2, oracle and mysql.
If you need super power take oracle, for all the reasons you mentioned daisho. If not I haven't run into any projects that mysql couldnt handle. Admittedly some of the work that oracle would do is done on the script but for the most part it can handle it.
I do find that you have to adjust the way you do things but it still holds up.
well you could always use access;)
One thing you need to do is to allow PostgreSQL utilize more ram. The default installation settings will only permit it to use just a few megabytes. Of course it will be slow while running that way. Give it as much ram as you can and it will fly.
Saying that PostgreSQL is slow is like saying that java is slow or that the only way to install linux is to copy all files from another box that already has it running. Those statements were true a long time ago, not any more.
