Realizm

I'm trying to figure out what method I should use for storing my information (and subsequently being able to bring it up, later) I'm going to describe my situation for you to see what you think... Here's how it is:

There's 4 of us right now, we all test the same products and need to write down certain info about each of them, general info regarding diffrent types (printer, computer, monitor).

Currently I am working on setting up some PHP pages that will write to a MYSQL database containing columns for each of the things of info our test pages need to insert. (serial number, model number, tester name for example)


Since different products have different test pages, I'm thinking I will make a seperate mysql table for each type of product, so like 3 tables (computers, printers, monitors). The page we testers will see will have an option for which of these items we are writing info down (pull down menu for monitor computer or printer) and then bring up a form for the appropriate item.

--


So, does this sound like an ok way of doing things? Writing all the information to their appropriate tables?


I'm kind of new to mysql and the concept of databases but this seemed appropriate at the time. NOW, though I've been doing a little reading about XML and am wondering if there is some way I should be using this instead?

I have yet to figure out how XML and Mysql (or any database) for that matter can work together, though I know it's got to be something really simple..


Like instead of writing to a mysql database, should I just store my info in XML files? For instance, should I make a php page that would write the text

<Tester name="Jim">
<item>HP 4200</item>
<serial>3424</serial>
</Tester> ?

into an XML file? One big thing I've yet to grasp is how an XML file gets its data. Whether forms write somethign similar to what I just made above to a .xml file or what..



I just absolutely can not comprehend how to use XML except I think MAYBE I should be using this instead of Mysql. I guess the obvious answer is "if you don't get it, you don't need it" but I would really like to get it so I could more understand why I do or don't need it. This has been a lengthy post, so thanks for your patience and answer if you read through this all..

RelaX

I am not very well versed in XML either (should still read that book) but I believe XML is only usefull if you intend to use your data by different programs or need to back it up regularly.
For your needs I would suggest a simple mysql database. Mucking around with XML would probably have an added cool factor but it will also deliver lots of unnecessary headaches.

__________________
The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents.
- Nathaniel Borenstein

mpedrummer2

I also vote the MySQL route, but mainly for the reason that I know/understand MySQL, and I'm in the same boat for XML that you are...I even bought a book about it, which told me how to do things, but I've never really grasped WHY I'd want to do them with XML as opposed to anything else.

MPEDrummer

__________________
My sig can beat up your honor student.

Cuball

if you want to read XML files you need some kind a parser (only know java based, SAX-Parser or DOM parser if i'm not mistaken)

but never used XML with php ... xml is handy if you want to distribute your information ... but sometimes it's just more a buzz word and are problems way better solved on the old fashioned way without using it

__________________
Let's GO

Realizm

k then, sticking with my mysql ways

nukeu666

mySQL is better as its pretty standard
xml is a new tech....browsers like firebird/fox dont fully support it yet

__________________
Why did the Comp. Engineer get X-mas and Halloween mixed up?
Because Oct(31) == Dec(25)