ok - thanks for all the replies. it looks like there are no real
drawbacks and plently of advantages in using MySQL instead of text files,
so i'll do the next project with it. one more question - is there a
concrete file that has the database in mySQL? like a file that I could
download and view
Hi Doug,
on 22/09/02 9:25 AM, Doug Parker ([EMAIL PROTECTED]) wrote:
> often i use text files at my data sources, delimted by the "|" symbol.
> i simply delimit the fields of each line, then when i need to open them,
> i open the text file, populate an array with each line, then explode the
> fi
Speed
Accessability
Features
Security
Performance
Simplicity
Reusability
Indexing
Record-Locking
To name a few.
however, in your situation, it's an existing application which is working
great and which no one has any complaints over. If it ain't broke, don't
fix it.
For your next application,
I was doing this too with good old AWK CGI scripts and text data files.
Once I imported the data into MySQL I said, "Well this is not much
benefit." Then I started sorting. Then I accessed the information from a
different application. Then I wrote a maintenance application so my
customer could
"Doug Parker" <[EMAIL PROTECTED]> wrote:
> i was wondering
> if there is anything i'm not thinking of that perhaps would push me to
> favor using php and mysql instead of the plain old text file.
It sounds like you're basically asking why one would want to use a
relational database. Standardiza
Well, one major advantage I have found using MySQL verses txt files is the
simple implementation of transactions, if you are doing multiple
transactions that are related, it is nice to simply "rollback" all other
statements if one fails or "commit" if they work. Of course you can do this
other way
6 matches
Mail list logo