An SQL abstraction layer thatâ€™s uglier than writing SQL.
Iâ€™m not sure we need another one of those anyway, but working on the assumption that someone does want this, I find fault with its execution in the following ways.
As far as the documentation allows a call, the API seems limited. Iâ€™m not sure it gives you full access to the power of SQL. Unfortunately, that cost does not come in exchange for clarity and simplicity: the interface is less than intuitive.
The documentation is rather unhelpful. It consists of two examples and a monosyllabic description of each function in the module. The examples are neither self-explanatory nor commented â€“ I can only guess what the code shown is supposed to do. An overview of the mechanics of the module or some description of the model of operation assumed is missing entirely.
The choice of namespace is the single worst aspect of the module: itâ€™s a database access wrapper rather than a database driver, so it belongs in DBIx:: instead of DBD::. I canâ€™t see anything that makes it particularly MySQL-specific, either, it looks fairly database agnostic.
By the time time you figure out this module, youâ€™ll probably be well equipped to write something equivalent more suited to your own habits yourself. In its current form, itâ€™s not likely to be useful to anyone other than its author.