Re: [Vfs-devel] class.DBI

[Tony K. <tk...@ca...>]

----- Original Message -----
From: "Abdul-Wahid Paterson" <ee...@we...>
To: <vfs...@li...>
Sent: Tuesday, June 06, 2000 12:49 PM
Subject: [Vfs-devel] class.DBI


>
> I have just been playing around with class.DBI and it seems to work fine
> with Postgres. I haven't tried any other database though but I am sure
> they work properly.
>
> There are a few issues around using class.DBI that we need to resolve.
> Manly due to the use of BLOBS for file storage. The way that PHP handles
> blobs for Postgres, Oracle and Informix is complete different. Mainly
> because there is no standard way that the databases handle blobs. I
> suggest that we have different functions for the individual databases that
> use blobs. Where should they go? May be we could still put them in
> some_database_wrapper.inc that gets included from by the db_wrapper.inc.

Why not look at integrating all of the database code from db_wrapper.inc
into class.DBI structure? We can just add all needed code to the DBD files.
All of the databases we want to support already have DBD files. We could
possibly drop some_database_wrapper.inc and db_wrapper.inc files all
together. Just move that code to the necessary class.DBD::some_database
files.

I'll spend some time today playing with the class.DBI code and comment more
on it later today.

> The structure would then be something like this:
>
> header.inc calls vfs_auth.inc, db_wrapper.inc and config.inc
>
> db_wrapper.inc calls some_database_wrapper.inc and loads class.DBI
>
> class.DBI loads the relevant class.DBD::some_database
>
> NOTE: we might also need to use the some_database_wrapper.inc to do other
> database specific functions like: using sequences, formating dates, etc.
>
> I suggest also that we create a directory /lib where we put the .inc
> files and the class.DBI stuff. We might have to change the class.DBI
> slightly because it calls the DBD driver from the current directory which
> won't be /lib but / becuase that is where the .php script will be running
> from.

To make the code and file structure cleaner I agree with the /lib directory
idea. I'm a sucker for keeping like files grouped into directories.

>
> Anyone else got any ideas on all of this?
>
> Regards,
>
> AW
>
>
>
>
> _______________________________________________
> Vfs-devel mailing list
> Vfs...@li...
> http://lists.sourceforge.net/mailman/listinfo/vfs-devel
>