eXtropia: the open web technology company
Technology | Support | Tutorials | Development | About Us | Users | Contact Us
Development resources
 ::   WebWare 2.1 (Perl)
 ::   WebWare 2.0 (Java)
 ::   Cool hacks
radical hacks
PHP Database WebStore  
sent in the following hack...

Gunther has suggested I write to you regarding a PHP/MySql interface to produce a database for the web store (database implementation). The hack requires that the user has MySql installed. However, it still requires an interface to be written to take the mysql database file to a flat file database suitable for web store. I am working on that at the moment. Shouldn't be too difficult. I just thought that someone might have already done it.

Attached is a tar file for the interface containing the files for this. The files work this way:

  • database_frame.html - this is the frames page that holds menu.html and main.html (at start up) and then the various other pages (add, update, delete) as they are loaded;
  • addplants.php3 - this page brings up a form for inputting new data
  • add_plants.php3 - this page shows the new data as it will appear in the database;
  • updatedatabase.php3 - this page brings up a page that allows you to identify which item in the database you want to amend, and the field that you want to change;
  • update_plants.php3 - this shows the amended details of the item just updated. Enhancements required (maybe) are to show all of the current fields of the database so that the right field can be identified to be updated
  • deleteplant.php3 - This is the interface to delete a plant from our database
  • delete_plant.php3 - this is the companion page for deleteplant.php3

Modifications that might be required - other suggestions needed - are:

  • A page that will allow the access details for the database to be generated for the "mysql_connect("hostname", "user", "password") routine. This would be via an include() file.
  • A page that will generate the name of the database to be accessed.
  • A variable for the name of the table that is being accessed
  • Change the names of the files so that they are a bit more generic
  • Documentation - as you can see, the routines are something that I have done for myself and I think it is all self-explanatory. I may be wrong.