Re: Potential for new database driver

Travis Elliott Davis <[email protected]>
Newsgroups gmane.comp.lang.perl.modules.dbi.sybase.devel
Message-ID <[email protected]>
Hi John and Lyle,

John, Apologies for the link not coming through.  The Blueprints documentation can be found at https://github.com/tinkerpop/blueprints/wiki.  Also, I apologize if I got the terminology mixed up.  My indention is to write a DBD for Blueprints in pure perl. 

Lyle, thank you for your feedback.  It definitely sounds like a good plan.  Writing it in perl first would be much easier in my case (C is not my strongest language).

Elliott


On Mar 4, 2013, at 5:21 PM, John Scoles <[email protected]> wrote:

> A pure perl version of the DBI already exists so I I take it you want to write a DBD::Blueprints?  There are a number of pure perl DBD however I am not sure what Blueprints is??? Can you give us a link to it so I can at least see what you are writing a driver for??
>  
> Cheers
> John
> > From: [email protected]
> > Subject: Potential for new database driver
> > Date: Mon, 4 Mar 2013 14:52:19 -0600
> > To: [email protected]
> > 
> > 
> > Hi All,
> > 
> > My name is Elliott Davis and I am relatively new to this list. I am interested in writing a driver for Blueprints. I imagine this working similar to the ODBC or the JDBC driver for DBI currently. I have read the DBI::DBD documentation (only once, not twice as instructed) and have found it very verbose. It seems that writing a C driver will be the optimal solution for speed but a pure perl driver will make the module more maintainable. If I were to work on the driver I think my goal would be a pure perl driver. The DBI::DBD documentation suggest an initial email to the dev list before pursuing code on any driver, so here I am. If anyone is currently working on this or is interested in working on this could you please let me know. 
> > 
> > Best Regards,
> > 
> > Elliott Davis
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.