RE: [PEAR-DEV] Database Schema Manager
- Aside from comments I was also begging for +1's :-)
PS: as binarycloud or metabase users might also be interested in this I
am also forwarding the proposal to them
> -----Original Message-----anymore.
> From: Lukas Smith [mailto:smith@...]
> Sent: Thursday, June 19, 2003 1:24 PM
> I am working on separating the Schema Manager in MDB into a separate
> The idea is that the new Manager will actually not require MDB
> Instead the main part of the manager is handling array structures thatdatabase
> represent a schema. These array structures can be build up one by one,
> merged, compared etc.
> Also the Manager can call a parser or a writer to read or write a
> I intent to provide the following parsers:
> - XML (old parser)
> - SQL (new)
> - MDB (old reverse engineering)
> and the following writers:
> - XML (new, used to be embedded in the manager)
> - SQL (new)
> - MDB (old default behaviour)
> There are all sorts of other parser and writers possible (someone else
> needs to decide if they are feasible enough to be implemented) like:
> - PEAR DB
> - WDDX
> - Excel
> - PDF
> - etc.
> Here is my preliminary work on the API:
> I don't know yet how to name it.
> Basically the schema manager does not require MDB by default anymore.
> Actually it is possible to write a writer and/or parser for any
> abstraction layer.
> So possible names are as follows:
> Lukas Smith
> Linn Zwoch Smith GbR
> Pariser Str. 44
> D-10707 Berlin
> Tel +49 30 83 22 50 00
> Fax +49 30 83 22 50 07
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
On 06/20/2003 10:20 AM, Lukas Smith wrote:
>>I am working on separating the Schema Manager in MDB into a separate
>>The idea is that the new Manager will actually not require MDB
I already thought of this but did not see much point in moving to a
separate package, except in the scope of PEAR. Since Metabase itself has
no dependencies on PEAR, this is not really relevant to Metabase.
I have plans to enhance the schema capabilities to implement things for
which I have personal needs. These capabilities will be implemented in
Metabase schema classes but I have no expectation when it will be done.
Maybe sooner rather than later, just can't say when.
Free ready to use OOP components written in PHP
> Aside from comments I was also begging for +1's :-)Great!
>> I am working on separating the Schema Manager in MDB into a separate
>> Also the Manager can call a parser or a writer to read or write aErh? Oh. Wait, like read in a SQL schema from a DB and write out XML, and
>> I intent to provide the following parsers:
>> - XML (old parser)
>> - SQL (new)
>> - MDB (old reverse engineering)
use that XML to create that schema on a new DB? heheheheh
>> - XML (new, used to be embedded in the manager)HARR! Excellent!
>> - SQL (new)
>> - MDB (old default behaviour)
>> - ExcelCSV, sure
>> Here is my preliminary work on the API:Looks good so far...
>> So possible names are as follows:SchemaManager is fine, eh?
FF'in great work, man.