The secure CMS.
Resources
Topics
- Home
- Development (317)
- Geeklog (209)
- Plugins (111)
- Themes (2)
- News (387)
- Announcements (248)
- Geeklog.net (31)
- Security (76)
- Spam (11)
- Summer of Code (26)
User Functions
Events
There are no upcoming events
What's New
Stories
No new storiesComments last 2 weeks
No new commentsTrackbacks last 2 weeks
No new trackback commentsLinks last 2 weeks
No recent new linksNEW FILES last 14 days
No new filesWelcome to Geeklog Saturday, May 18 2013 @ 03:04 PM EDT
What Database System do you prefer?
1/1: What Database System do you prefer?
| MySQL |
 468 (74.64%)
|
| PostGres |
82 (13.08%)
|
| MSSQL |
22 (3.51%)
|
| Oracle |
34 (5.42%)
|
| ODBC |
6 (0.96%)
|
| Berkly |
2 (0.32%)
|
| Other |
13 (2.07%)
|
Other polls | 627 voters | 10 comments
The following comments are owned by whomever posted them. This site is not responsible for what they say.
JJ
I\'d like to see GeekLog ported to Postgres, or perhaps if we make our own database layer (or use an existing solution) we can just choose between mySQL and Postgres in the config file. That way I can make an Arabic site using GeekLog :-)
If anyone interested please email me.
But of course if someone else is already working on it, ignore this comment... I have other things to work on too.
BTW, why do you hate PostgreSQL?
Chris
The thing is even if you start off with MySQL, eventually sites grow and you start adding advanced features that need a more mature DB engine.
I have had that experience. Initially, PG seemed to have too much unneeded complexity, the configuration was a bit more esoteric (hey we are talking DBMS's here :-) and many of the non-INSERT/UPDATE/SELECT commands were different.
But things like transactions are actually massively more useful that some MySQL advocates would make out. You don't need to be writing a banking application to make transactions extremely useful. Sequences also are a lot more useful than AUTO INCREMENT.
Interesting reading on the pros and cons can be found in this PHPBuilder article. Keep in mind that since that article, many improvements have happened to postgres, including the abolishment of the 8K row limit (I beleive) and stability is now rock-solid. Performance is now right up there too.
I still have lots of respect for MySQL, and I'm using it for my current DB-Driven project. It's speedy, lightweight, and in this particular case it does everything I need.