“dba” 0.3.0

Found a problem with the way I was testing logical statements (rs[0] != NULL) which lead to finding that some of the tests weren’t being, well, tested. After fixing that, I found the SQLite interface was reading one too many rows.

Also turned on -Wall and -Werror for the non-MSVC builds, to catch any errors I was missing – I found a few minor casting problems which I also fixed. This version is the first “healthy” version. It also seems to compile and work quite happily under MSVC.

– Oliver

“dba” v0.2

Version 0.2  2010/03/01 [ Status:: MySQL: working; SQLite: working ]
  1. Completed a number of incomplete functions.
  2. Brought the SQLite interface up to working status.
  3. Some convenience functions (variadic constructors).
  4. Fixed numerous bugs.
  5. Significantly bolstered “main.cpp”

Welcome back, MySQL :)



Farewell, MySQL

There was all kinds of speculation about whether or not Oracle’s purchase of Sun – and thus MySQL – would mark the end of the era of free MySQL…

Well, in just the last week or two it seems that MySQL Community Edition has dropped off MySQL’s site. It had done soonce, briefly,  in an earlier reshuffle a couple of years ago but came back, so I’ve spent the last 40 minutes searching around their site trying to find it.

It’s gone.

It’s not on the front page…

It’s not under “Products”

It certainly isn’t under “Enterprise” anywhere

And it’s not under “Why MySQL”

Could this be why?

If you want MySQL Community edition, you’re going to have to head to their “developer” site, So it’s not quite dead yet.

Wonder if it’ll come back when they stop getting 65,000 downloads a day because people can’t find the link, and go to Postgres/SQLite instead?

Nearly done with PreparedStatement

It’s been a really busy week – starting out with me going locking down on Monday and working from home to get a whole bunch of stuff blasted out without having to go cowboy.

Somehow, inbetween everything else, I’ve managed to get a little ‘recreational coding’ out of the genuine need to get prepared statements integrated into the codebase for what we’re doing with the auth process.

So far, I only need data modifying statements, but the natural progression is a general encapsulation that will also support call/select etc. (Right now I never even both fetching the result set because none of my queries needs to).