caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Michael Neumann <uu9r@stud.uni-karlsruhe.de>
To: caml-list@inria.fr
Subject: Re: DBI (was : [Caml-list] sybase interface?)
Date: Sun, 13 Apr 2003 14:23:10 +0200	[thread overview]
Message-ID: <20030413122310.GA23723@rz.uni-karlsruhe.de> (raw)
In-Reply-To: <Pine.LNX.4.53L.0304130640380.3128@ontil.ihep.su>

Vitaly Lugovsky wrote:
> On Fri, 11 Apr 2003, Christophe TROESTLER wrote:
> 
> > A while ago, it was said on this list that a common database
> > interface
> > (? la Perl DBI) would be nice.
> 
>  Nice? May be. But impossible. E.g., for Oracle you have to use
> prepared statements with variables substitution, when in
> Postgres there is no need to mess with this stuff - performance
> is good enough if you create a new statement for every request.
> 
>  Postgres have asyncronous messages. OCI don't. Other database
> interfaces could be even more different...

IMHO many people just want to issue their SQL commands and get
back the resulting rows, without writing too much code. And they 
don't use many of the special features, like asynchronous messages etc. 

If someone want's to start a DBI-like interface, please also have a look
at Ruby/DBI (I'm the creator of it). 

http://ruby-dbi.sf.net

And it's DBI specification:

http://ruby-dbi.sourceforge.net/DBI_SPEC.html

Also take a look at Python's DB API.

> > Are there people interested on this list?  Personally I don't
> > have

Even if I'm not a OCaml guy, I'd like to help with the interface
as much as I can.  

> > much time to contribute but as I will be soon in need of using
> > DB, I
> > am willing to make an effort.
> 
>  I have no problems in using two quite different APIs in a
> mid-layer - Oracle and Postgres. And I don't think I'll ever will
> try to use any kind of generic interface. I ate this shit with
> JDBC, and I don't want it any more...

You can't compare JDBC with DBI. DBI is a very pragmatic approach to
a database interface, without much overhead (in terms of additional code), 
whereas JDBC doesn't help write less code. I don't like to read hundreds
of pages, before I can issue a simple SQL statement. With DBI, it's just
5 lines of code.

Regards,

  Michael

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2003-04-16 16:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 13:35 [Caml-list] sybase interface? Michael Wohlwend
2003-04-11 17:18 ` DBI (was : [Caml-list] sybase interface?) Christophe TROESTLER
2003-04-12 11:48   ` Matt Gushee
2003-04-12 20:30     ` Erik Arneson
2003-04-12 22:33       ` Seth Kurtzberg
2003-04-12 18:57   ` [Caml-list] Re: DBI cashin
2003-04-13  2:47   ` DBI (was : [Caml-list] sybase interface?) Vitaly Lugovsky
2003-04-13 12:23     ` Michael Neumann [this message]
2003-04-14  1:23   ` Nicolas Cannasse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030413122310.GA23723@rz.uni-karlsruhe.de \
    --to=uu9r@stud.uni-karlsruhe.de \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).