Jump to content

Recommended Posts

For holding temporary information, reading lists, or any data that you don't need to search through, flat files are fine to use. It takes less time to develop something to work with.

 

If you are concerned with not losing data, being searchable, multiple or complex queries, the database is the better way to go. You have a lot more control over it as well.

 

sqlite is a mix of the 2, it keeps everything in files but also acts like a database.

http://www.sqlite.org/

 

 

Link to comment
https://forums.phpfreaks.com/topic/237683-flat-file-or-sql/#findComment-1221474
Share on other sites

Most times using a database is easier for me and more efficient but there few exceptions.

Properties files (either application properties or languages application messages) and application scope cashing.

In latter case I use flat files where objects have already been serialized. Of course in both cases those files shouldn’t be in public_html but in a protected directory above (in a sub directory of src for example).

Link to comment
https://forums.phpfreaks.com/topic/237683-flat-file-or-sql/#findComment-1221530
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.