caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Benjamin Geer <ben@socialtools.net>
To: Vitaly Lugovsky <vsl@ontil.ihep.su>
Cc: Josh Burdick <jburdick@gradient.cis.upenn.edu>,
	Richard Jones <rich@annexia.org>,
	Inria Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] PostgreSQL-OCaml 1.0.1
Date: Fri, 30 Jan 2004 10:24:45 +0000	[thread overview]
Message-ID: <401A30ED.6090007@socialtools.net> (raw)
In-Reply-To: <Pine.LNX.4.58L.0401301117030.12020@ontil.ihep.su>

Vitaly Lugovsky wrote:
>>   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.
> 
>  It was already discussed here. The conclusion was: BAD IDEA. No
> way to work efficiently with different DBs using the same
> approach.

In the company I work for (a large financial software vendor), the 
unanimous answer would be 'we don't care if it's less efficient; nothing 
else is acceptable.'  Our customers insist on being able to use our 
products with whatever database they prefer (and certainly our 
competitors' products can do this).  We simply cannot afford to rewrite 
and maintain all our database-related code for every one of those 
databases.  For us (and, I think, for most software vendors, certainly 
all the ones I've worked for) the additional abstraction is well worth a 
slight loss of efficiency.  It is quite efficient enough for us.  The 
lack of a standard database API is one of the things that, 
unfortunately, would make it very difficult for me to convince my boss 
to let me use Caml.

Ben

-------------------
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:[~2004-01-30 10:24 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
2004-01-30  7:37           ` Shawn Wagner
2004-01-30  8:21           ` Vitaly Lugovsky
2004-01-30 10:24             ` Benjamin Geer [this message]
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=401A30ED.6090007@socialtools.net \
    --to=ben@socialtools.net \
    --cc=caml-list@inria.fr \
    --cc=jburdick@gradient.cis.upenn.edu \
    --cc=rich@annexia.org \
    --cc=vsl@ontil.ihep.su \
    /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).