From: Vitaly Lugovsky <vsl@ontil.ihep.su>
To: Benjamin Geer <ben@socialtools.net>
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 14:25:12 +0300 (MSK) [thread overview]
Message-ID: <Pine.LNX.4.58L.0401301419330.17414@ontil.ihep.su> (raw)
In-Reply-To: <401A30ED.6090007@socialtools.net>
On Fri, 30 Jan 2004, Benjamin Geer wrote:
> > 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).
And what's a problem? Write a portable layer, which provides
YOUR application-oriented abstractions. Writing database-related
sub-layer would be easy enough yet, but you will not pay the
price of the efficiency.
> We simply cannot afford to rewrite and maintain all our
> database-related code for every one of those databases.
It can't be so large. Fine-grained layer always contains no more
then a dozen of low-level entities.
> 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.
I've heared a lot of evil words from the industry programmers
about the "good enough" efficiency of the JDBC. And, they're even
have no alternatives, poor ones...
> 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.
You may provide one, your own, which is limited to the standard
JDBC-like abstraction level, it would be easy to support, if you
don't want to write a higher level abstractions (don't forget -
you'd pay much more for the problems with SQL incompatibility -
so there is no damn need in the JDBC-level layers at all). But
why the maintainers of that DB bindings, like me, would follow
someones "standard" limitations?
-------------------
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
next prev parent reply other threads:[~2004-01-30 11:26 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
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 [this message]
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=Pine.LNX.4.58L.0401301419330.17414@ontil.ihep.su \
--to=vsl@ontil.ihep.su \
--cc=ben@socialtools.net \
--cc=caml-list@inria.fr \
--cc=jburdick@gradient.cis.upenn.edu \
--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).