Well, first, I don't know the original motivation for opendbx... Maybe Norbert wanted to (sort of) decouple his C application from a specific driver. The thing is that it's not simple to track its users.

Then, alive as "it compiles and it works in latest versions of OSs", it is :). I did the whole compilation for the three platforms and drivers about a month ago.

On the other side, alive as "it is adding new features from time to time", it's not. Maybe because database drivers do not evolve also too much, nor they change their API. The latest changes, from about a year ago were some bugfixes to ODBC and fixing some compilation stuff for windowze.

Following EstebanL's comment, we would like to get completely rid of it, but so far it's useful to connect to databases that otherwise we couldn't, like oracle. For other vendors, such as Mysql or PGsql, there are the pure smalltalk versions of the drivers, which are probably better from the maintenance point of view.

Guille



On Thu, Dec 12, 2013 at 3:35 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
is not incredibly used, but it is not completely dead :)

anyway... one of our many many projects is to drop opendbx (by moving that layer to pharo itself)... but that's for the future (probably far future).

Esteban�






On Thu, Dec 12, 2013 at 2:30 PM, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
As a side question about my dependency issues...

Is the OpenDBX project still active? Not its Smalltalk side, I mean...
the core project.

To me it seems like it was a great attempt to have something similar
to ODBC but for all platforms.
But I'm not seeing a wide usage of it in the wild.

Seems like everybody else is happy with their JDBC, DBI and similar
"DB layers" on the language side.


Regards,

Esteban A. Maringolo