Alan McDonald wrote:

>> Firebird and Oracle both tend to need to same mods so as soon as
>> we sorted
>> that out with bitweaver then people were happy even to take on
>> board the field
>> name changes to eliminate reserved words.
>>
>> How far have you gone - do you need help getting the datadict
>> stuff working as
>> the xml ADOdb bit working for Firebird would be nice to put to bed.
>>
>> --
>> Lester Caine - G8HFL
>
> well, it's definitely not parsing correctly. I've managed to track thru some
> if the steps but I can;t quite work out where the datadict file is(not)
> being called correctly.
> Alan

I'll have a look over the weekend Alan. I've got an important meeting Monday
that I need to finish some work for first ;)
I think I had some other mods to the main datadict code ...

in /set-up/index.php
$this->mDataDict = & NewDataDictionary($this->mDbConnection);

becomes

$this->mDataDict = & NewDataDictionary($this->mDbConnection, $data['db_type']);

This will pick up the firebird datadict code rather than ibase, but the
$this->mXmlSchema->ExecuteSchema(); in the next block is still not working
correctly, and does not create the tables.

The way flyspray generates the pages is a right pain. I can't simply drop
print statements in to see what we are getting at the next stage like I do in
my own code ( in fact I have a vd() function that provides an elegant view of
the dump )

BECAUSE I can't debug their code my next step would be simply to build the
tables manually using the info from
/set-up/upgrade/0.9.9.2/flyspray-install.xml but it may be worth asking the
question on their list as to HOW they debug ;)

They are using 'AUTOINCREMENT' on every table which will probably be the
problem. On bitweaver the 'non' Firebird guys found out early on that in order
to do the job properly they needed the VALUE of an Id before populating the
record and so MOST auto fields have been stripped and generators are simulated
where they are not available :) My datadict code correctly builds a table and
creates a generator and adds the trigger code when AUTO is used in the non-XML
build process, but I doubt that is being picked up properly in the XML one. It
would probably not take long to fix if I could only SEE the data :(

So much for leaving it till the weekend ;)

--
Lester Caine - G8HFL
-----------------------------
Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://home.lsces.co.uk
MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Firebird Foundation Inc. - http://www.firebirdsql.org/index.php