: The fastest way would be to use C.
: But the reason for using a DB would be.
: 1. Access to data. You could use PhPMyAdmin or some thing you
: put together
: to update the policy so making managing the data easy (possibly so non
: tickers should make changes).
: 2. If the data you are getting needs to be retrieved relationally.
:
It depends on the complexity of the policy too. If its has several
sections, and each section needs to stand out, you will either have
to use some markup (doesn't have to be HTML) to tell those sections apart,
or store each section as a different raw of a table using a little more
complex
DB design. This also requires a little more complex SQL query to retrive
them.
I would probably use some minimum markup to mark the sections, and store
the whole policy in a single cell.
Good luck
Sherzod
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
