On Mon, Dec 08, 2003 at 09:41:46AM +0000, Nigel Metheringham wrote:
[...]
> I have wondered whether it would be better to indirect the database
> issue by putting everything through a database adaptor layer - theres
> one thats been discussed before that I cannot remember the name of at
> this moment. However that would act as a database interface/caching
> layer and also hold a small number of database connections open allowing
> connection caching/sharing.
[...]
There are more than one (e.g. libgql0 or gda) but the unified access
modules themself are often bigger/fatter than linking against mysql
and postgresql.
Quoting myself from a mail sent to debian-devel in April:
| Just checking the dependencies and sizes on woody, neither libgda nor
| unixodbc are more leightweight than linking directly against mysql
| and pgsql *at* the *same* *time*.
| 217348 17. Jul 2002 /usr/lib/libmysqlclient.so.10.0.0
| 65636 31. Mär 2002 /usr/lib/libpq.so.2.2
| 60464 24. Mär 2002 usr/lib/libgda-client.so.0.0.0
| 148400 24. Mär 2002 usr/lib/libgda-common.so.0.0.0
| 472824 13. Apr 2002 usr/lib/libodbc.so.1.0.0
|
| gda looks small but its interlibrary dependencies on woody are
| completely over the top (complete GNOME), the version in sid is iirc
| sane, but still pulls in libglib1.2, libxml1 and libxslt1, which makes
| it bigger than libmysqlclient+libpq.
"woody" is Debian/stable, "sid" is Debian/unstable.
cu andreas
--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"
