caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Josh Burdick <jburdick@gradient.cis.upenn.edu>
To: Richard Jones <rich@annexia.org>
Cc: Inria Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] PostgreSQL-OCaml 1.0.1
Date: Fri, 30 Jan 2004 00:50:41 -0500	[thread overview]
Message-ID: <4019F0B1.6050204@gradient.cis.upenn.edu> (raw)
In-Reply-To: <20040129200653.GA14321@redhat.com>

Richard Jones wrote:

>>From my point of view (mod_caml depends on the postgres support) it
>would be nice to have just one library to work with.  Perhaps combine
>the best features of both into a single release?
>  
>
   If there's going to be a "new improved version", I think maybe it 
should work with multiple databases.  ODBC, JDBC, and DBI all attempt 
this.  There could be a signature (perhaps called "DBI" to appeal to 
Perl people , and structs Postgres, MySQL, Oracle, etc., which implement 
this.
   Different databases have varying levels of standards-conformance, of 
course, and there's all sorts of variation between databases, so I 
wouldn't expect one to be able to take one OCaml program written with 
this interface, and blithely switch databases, especially for 
complicated stuff.  But you should be able to write simple "select * 
from customers"-type queries, against any database, without totally 
re-working your OCaml code.
   Database independence seems like a good goal to move towards.  If 
there's going to be potential interface changes anyways, now might be a 
good time to plan a more general interface.
   (I used the old Postgres module, and it worked well.)

   Josh Burdick
   jburdick@gradient.cis.upenn.edu

>Rich.
>
>  
>


-------------------
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


  parent reply	other threads:[~2004-01-30  5:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28 18:32 Markus Mottl
2004-01-28 22:44 ` Stefano Zacchiroli
2004-01-28 23:21   ` Markus Mottl
2004-01-29  9:38     ` Sven Luther
2004-01-29 18:18     ` Alain.Frisch
2004-01-29 20:06       ` Richard Jones
2004-01-29 23:36         ` Markus Mottl
2004-01-30  5:50         ` Josh Burdick [this message]
2004-01-30  7:37           ` Shawn Wagner
2004-01-30  8:21           ` Vitaly Lugovsky
2004-01-30 10:24             ` Benjamin Geer
2004-01-30 10:47               ` Richard Jones
2004-01-30 14:58                 ` Gerd Stolpmann
2004-01-30 15:46                   ` Richard Jones
2004-01-30 11:14               ` Markus Mottl
2004-01-30 11:25               ` Vitaly Lugovsky
2004-01-30 11:41                 ` Benjamin Geer
2004-01-30 16:44               ` Alex Baretta
2004-01-30 16:49                 ` Benjamin Geer
2004-01-30  8:23           ` Alain.Frisch
2004-02-01 21:03   ` Alain.Frisch
2004-01-30 12:02 Richard Jones
2004-01-30 12:15 ` Benjamin Geer
2004-01-30 12:23   ` Richard Jones
2004-01-30 12:30     ` Richard Jones
2004-01-30 12:43     ` Benjamin Geer
2004-01-30 12:56     ` Benjamin Geer
2004-01-30 13:22       ` Richard Jones

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=4019F0B1.6050204@gradient.cis.upenn.edu \
    --to=jburdick@gradient.cis.upenn.edu \
    --cc=caml-list@inria.fr \
    --cc=rich@annexia.org \
    /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).