Writing our own parsing thing is out of question. The group has finalised to use a proper DB rather then writing our own code. Moreover, we believe that the code written by a good DB engine would be much more efficient then writing our own module and we are no database experts :) So now its a question of which XML DB to use. After Christophers mail, we would give Oracle a run in next weeks. Lets see.... On 1/26/07, Edward Vermillion <evermillion@xxxxxxxxxxxx> wrote:
I would imagine that parsing the XML file you get once a month and storing the information in *some* kind of "real" database, whether it's oracle, mysql, postgresql or whatever would give you better performance than parsing the XML on each page request. Unless the XML is of a trivial size of course, but I didn't get that impression from the original post. Just a thought... On Jan 26, 2007, at 2:24 PM, Ritesh Nadhani wrote: > Thank you. > > I dont think we have the computing power for this project to use > Oracle 10g. Also, the system is too big and nobody out here has > actual knowledge of Oracle but anyway I will keep it in mind. > > Ritesh > > N.A.Morgan@xxxxxxxxxx wrote: >> Ritesh, >> Don't know of a suitable XML database to use with PHP, but I could >> recommend using Oracle 10g. There are built in XML services that >> should >> help with your project. Furthermore, PHP has a well documented >> Oracle >> interface (OCI8) just for this. To handle the XML though, you would >> probably need to get to grips with PL/SQL, Oracle's own stored >> procedure >> and trigger language. And the best part, you could use OracleXE for >> free, although it only gives you a database with up to 4GB user >> data, up >> to 1GB of RAM and use of only one processor in a multi-processor >> environment. >> Regarsd, >> Neil >> -----Original Message----- >> From: Ritesh Nadhani [mailto:riteshn@xxxxxxxxx] Sent: 26 January >> 2007 06:43 >> To: php-db@xxxxxxxxxxxxx >> Subject: PHP with a XML database >> Hello all >> As part of my research under my professor I have to implement a web >> interface to their benchmarking data. >> PHP is the chosen web language but we are little worried about the >> database. The benchmark data comes to us in XML format (e.g. >> http://www.matf.bg.ac.yu/~filip/ArgoLib/smt-lib-xml/Examples/ >> FolEq1.xml) >> . >> We have to implement an interface to query them, get data, update >> etc. >> We even can change schema in the form of attributes. . The data size >> would be around 100 MB each XML with around 100 different XMLs. >> The load would be max 5-10 users any given time, batch updates once a >> month and heavy load prolly 2-3 times a month. Mission criticality is >> not important, we can get it down sometimes. Which db would you >> suggest? >> i did google research and as of now - I like eXist, Sedna (they >> seem to >> have good PHP wrapper support) and TImber. >> Any suggestions? >> Ritesh >> -- >> PHP Database Mailing List (http://www.php.net/) To unsubscribe, >> visit: >> http://www.php.net/unsub.php > > -- > PHP Database Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php >
-- Ritesh http://www.riteshn.com -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
