RE: [PHP] MySQL vs. basic text file
| From: | Steve Bradwell | Date: | Mon, 23 Sep 2002 15:39:43 +0000 |
| Subject: | RE: [PHP] MySQL vs. basic text file | ||
| Groups: | php.general | ||
| Request: | Send a blank email to php-general+get-117294@lists.php.net to get a copy of this message | ||
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 ways but the simplicity is nice. Although I am still a newbie, I would
also have to say there would be a speed issue, if you only wan't one row
returned versus reading enire file into memory then walking through it one
at a time, mysql's indexing can greatly speed this process up.
HTH,
Steve.
-----Original Message-----
From: Doug Parker [mailto:drparker@clam.rutgers.edu]
Sent: Saturday, September 21, 2002 7:26 PM
To: php-general@lists.php.net
Subject: [PHP] MySQL vs. basic text file
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
fields for each to get the corresponding values. i use this method for
catalogs - and even backend interfaces, for which the client can
add/edit/delete products. everything seems to be working fine, and
there doesn't seem to be a need for MySQL or anything. 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.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php