RE: [PEAR-DEV] Re: DB_Torque Classes
| From: | Hundiak, Arthur | Date: | Mon, 26 Jan 2004 14:12:54 +0000 |
| Subject: | RE: [PEAR-DEV] Re: DB_Torque Classes | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-25283@lists.php.net to get a copy of this message | ||
-----Original Message-----
From: Alan Knowles [mailto:alan@akbkhome.com]
Sent: Saturday, January 24, 2004 8:44 PM
To: pear-dev@lists.php.net; Hundiak, Arthur
Cc: 'pear-dev@lists.php.net'
Subject: [PEAR-DEV] Re: DB_Torque Classes
From what I saw this looks really good -
Couple of quesitons?
- Does it handle native types - eg. database specific types... (the xml
schema seems to be quite rich (so I presume it probably does)
REPLY (from Art H): There are more data types available. I only implemented
the ones I needed. And it was a poor implementation. There should probably
be one class per data type which in turn would allow plugging in more
complex code such as the MDB2_Date class. I suppose database specific types
could be added though the existing torque schema does not directly support
them.
- Is there any Database Query->XML schema utility.. One of the realities
of development that I found using MDB schemas, was that I did the
initial design OK in it, but after 6 months work - I had hacked the
database around so much, the original XML was no longer valid (and
really needed regenerating from the DB..)
.. hence remembering some of the database specific stuff like sequence
names, etc. would be very usefull...
REPLY (from Art H): There are some Java tools that can do this. And I would
think that some existing php tools could be adopted as well. The motivation
behind the DB_Torque/DB_Structure classes is to have a single internal
interface for describing RDB structures. There could be several
reader/writers (Torque xml format, MDB2 xml format, DB_DataObject ini format
etc.). Various tool would then use this internal format for doing their
stuff. This would promote sharing data between the tools and perhaps
prevent some duplicate development.