RE: [PEAR-DEV] module for XML databases
| From: | Dave Viner | Date: | Thu, 07 Nov 2002 18:46:55 +0000 |
| Subject: | RE: [PEAR-DEV] module for XML databases | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-10563@lists.php.net to get a copy of this message | ||
I've been using Xindice for several months... Xindice has a PHP
administrative interface that I redesigned to be more fully functional. but
I think a pear extension for it would be cool.
dave
-----Original Message-----
From: Richard Samar [mailto:email@richard-samar.de]
Sent: Thursday, November 07, 2002 9:29 AM
To: pear-dev@lists.php.net
Subject: Re: [PEAR-DEV] module for XML databases
Nigel Armstrong wrote:
> [...]
>
> I think the answer to the question "should XML databases have their
own classes
> or be implemented under DB or MDB" is "both".
>
> The former classes are for programming when one wants to take
advantage of the
> special features of XML databases, the latter are when one has some
existing
> code that uses DB or MDB for storage.
Will you do this integration? And surely all the communication
which is necessary with the responsible maintainers?
I probably won't as I am neither into DB nor MDB.
The APIs of accessing the XML DBs should be kept simple and usable.
This is my idea behind it. If you want to add it to a special
module from the background it would make even more sense to
add them to XML than to DB.
In addition I would like to ask ppl here about their background
and experience with XML databases. Tamino and Xindice by now
are so specific (from their features) that I didn't start writing
an abstraction for both of these.
Now we are talking about an integration with MDB or DB. With this
decision the modules for accessing XML databases will be avaible
by the end of next year.
> Both might be used alongside one another on a single project, for
example if you
> were writing a new application on top of an XML database but you want
to use
> Mail::Queue at the same time. Having both sets of classes means a single
> underlying database can be used.
Let me explain that: if you use XML databases you understood
the deficiencies of RDBMSs and that is why you don't want to use
these for your projects. There are sure similarities like
opening a connection, making a query etc. But this is a too abstract
view on things. The approach of solving problems is a completely
different one and an integration into DB or MDB is pointless.
-moh
--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php