Sun, mysql and postgresql
You are welcome to extract excerpt of this article, but do not copy it entirely on your blog/web site.
You are only allowed to use this post content in an printed article or a newsletter by clearly exposing the source URL of this article.
So, Sun have acquired MySQL....
A rather surprising move, that not many peoples have sen coming, but interesting nonetheless.
What strikes many peoples (well, more developers) mind is "What will be the future of sun support to postgresql?"
I seriously hope that it won't change. Sun is already one (if not The) biggest supporter and resource giver to the postgresql project, and letting everything by would be extremely disappointing for many peoples.
Fortunately, posts from Jonathan Schwartz and Josh Berkus blogs both looks reassuring.
To sum it up, Sun acquired MySQL, but mainly to consolidate it's position on the data-center ground.
This makes sens to me, as they already where providing postgresql support.
After all, MySQL have a large community and is widely used by many small to medium enterprises.
It would be stupid to ignore those potential clients from sun.
I've waited a few hours before writing this up, and I feel rather relaxed today about what I see.
I don't think that much will change from the buyout of MySQL, and I like it that way.
MySQL is well suited for some tasks, postgresql does a fantastic jobs in some areas ( I think triggers, compiled functions, access authorizations, GIS ...), and sometimes sqLite is just the tool needed.
There is no good for everything database available, just tools with their pluses and minuses.
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically each day to your feed reader.

No comments yet.
Leave a comment
Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>