Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.8.6

Bug #9435 Having initialization and declaration in seperated files doesn't work anymore
Submitted: 2006-11-23 20:32 UTC
From: dufuz Assigned: ifeghali
Status: Closed Package: MDB2_Schema (version 0.7.0)
PHP Version: 5.1.6 OS: FC 6
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 17 - 2 = ?

 
 [2006-11-23 20:32 UTC] dufuz (Helgi Þormar)
Description: ------------ From version 0.6.0 and down then I was able to keep the initialization and the declaration in seperated files (very convinient) but that doesn't work anymore, I can't pin point the problem but it seems it's only reading the initialization file and thus thinking that there aren't any fields to work with. Having gone over most of the code in MDB2_Schema then I see that this should be working properly but it breaks down at some odd place and my time is limited but the function in question _should_ support it, maybe the XML_Parser is acting up or maybe something about the new end handler. Maybe this might push you in the right direction (note it's been long since I dove into the schema code) but it looks odd where validateTable is called ... Test script: --------------- $variables = array(); $structure = 'file1.xml'; $data = 'data.xml'; $manager->writeInitialization($data, $structure, $variables);

Comments

 [2006-11-25 18:55 UTC] ifeghali (Igor Feghali)
as we talked on IRC, I am going to take a few weeks before I can fix it.
 [2006-12-16 04:01 UTC] ifeghali (Igor Feghali)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.