Well, as you know the RAD Studio 2010 was released. Let’s answer to some questions which folks raised in forums. One of the most discussed problems (besides SA notifications) was the database support. And this isn’t odd at all since most of us use Delphi as a Database Development tool. No, I don’t imply that Delphi cannot be used in other applications, I just wanted to point out how important is Database support in Delphi. But let’s look a little bit closer…
The main complaint of some folks was about (lack of) support for their favorite database engine. As perhaps, you know, in this release there is no official SQLite and PostgreSQL support. Well, giving in account that we have already a new DBX driver in this version (Firebird) and the number of votes for PostgresSQL and SQLite compared with the ones for the Firebird DBX driver (which was #1 in QC with more than 1000 votes on all reports – duplicates, variants etc.) is a quite expected result.
A small parenthesis to prevent flames: Guys, the status ‘Closed’ on the PostgreSQL QC item means (if you look closer) that it is ‘Deferred to next release’. They mark it in such a way in order to not see it in the current release. When a new release cycle begins these are taken in consideration. Nothing to worry about. Just vote on the above reports if you think that it’s appropriate.
Is this odd? Are they some isolate users? No, they aren’t. According with our polls from this post (btw, thanks A LOT for participating, you gave a very valuable feedback), we have the following results at the question What databases do you use in your Delphi programs?
Note: The list doesn’t contain other database engines which had lower number of votes.
Well, I think that the things are pretty clear. PostgreSQL and SQLite are the first officially unsupported databases from the list. And even if they aren’t officially supported they are used by you. Of course, now when we’re heading to cross-platform the importance of these database engines will grow, and the importance of Windows only (R)DBMS is expected to drop (MS SQL , Access, Paradox / dBase etc.). But there are other interesting things to note:
- Firebird + MS SQL + mySQL accounts more than 50% from your preferences with Firebird as clear leader. (MS SQL + mySQL = Firebird percentage). Closely follows Oracle and Access (!). Now, with the acquisition of SUN the things (perhaps) will change.
- There are very few ‘others’ – (less than 1% – not pictured) sign that we’re on a mature market
- The Delphi-born databases are doing well imho – DBISAM, Nexus, Advantage are all grouped in a tight competition
- Access, Paradox / dBase – guys, even if I can see value in having Access databases, perhaps is time to move on. Just a small hint…
- Interbase is doing (also) well – much better than eg. Sybase
Please note that the above results doesn’t mean that one database engine is bad and the other one is good. Eg. the IBM’s Informix is one of the best OLTP databases around. The above results just show your preferences. The same stands about the next pool: What communication layer do you use?
Here the things are quite different. Here is a big ‘Other’ slice composed from many third party solutions (the folks want mostly *DAC things) – sign that the market shape is quite different from the above. Things to note:
- Embarcadero’s offerings are doing quite well – DBX is 2nd ( 🙂 ) (also, ADO is Embarcadero’s implementation), DataSnap has a respectable 7% ( 🙂 ) (mind you this is only an n-Tier solution so, the ones who choose this one must (most probably) choose also another solution), IBX and, of course, BDE ( 😦 ). Guys… time to move on. What holds you back?
- Also we see a bunch of Firebird/Interbase solutions which are high in ranking: FIBPlus, and a little bit lower IBX and IBObjects almost in par.
- Microsoft solutions are in use by many developers (ADO and ODBC – still ODBC? why?) but I really don’t know how much ‘cross-platform friendly they’ are… 😉 At least some from us should start thinking in this way from now on, isn’t?
At the end I wish to thank you all once again for the great feedback (more to come) and feel free to discuss the above.