Rudy Lippan wrote:
On 11/03/2010 10:08 PM, Darren Duncan wrote:
Darren Duncan wrote:
Rudy Lippan wrote:
Does anyone know if there are any DBD::drivers that do not use some
variant of SQL? I ask because I am planing on implementing the driver
using mongoDB's native query language initially, but having a
query_language attribute so that It would be possible to add SQL later
if desired/wanted.
As I understand it, DBI is agnostic to the database query language in

At least that is what the docs say :)

Ignoring what existing DBD:: support, do you see anything in the fundamental DBI-defined API that is SQL specific and has no analogy for other DBMSs?

In my own effort to rewrite DBI itself (Muldis::Rosetta::Interface[|::*]) which wasn't constrained to just SQL-think, I thought through various matters and still ended up with fundamentally the same API that DBI has (Machine=driver, Process=connection,...) and in particular found that it could easily be agnostic to the DBMS query language and essentially just pass it through. The largest design difference I have is that while DBI's interface wraps its driver counterparts, Muldis' interface is just a set of roles which its drivers ("engines") compose and users invoke the driver/engine directly; hopefully DBIv2 will do likewise rather than continuing the wrapper approach.

Furthermore, to answer your other question ...

I'm not aware of any existing DBD:: that doesn't take some variant of SQL.

If that is the case, let the hate mail begin...

What hate mail, for what reason?

-- Darren Duncan

Reply via email to