mySQL database vs. text database version

Anonymous
2002-11-17
2002-11-19
  • Anonymous - 2002-11-17

    I'm just curious what the benefits of the mySQL version are.

    Is it faster? Does it scale more efficiently? I can see how some of the text files in the database version could get very large overtime.

    How much will it affect performance to have a 1-2MB text file? Does the mySQL database version have this same issue?

    Just wondering what the performance benefits are.

    Thanks!
    Chris

     
    • Nobody/Anonymous

      With the text based version, you'll probably loose your data after time. If you have 2 users, or more, accessing the files at the same time. let's say a nth user reads the pistures file while another is writing to it, the nth user will get an incomplete file. When it's time for the nth user to write it back, only the part that was written when he read it will be written back. So you loose the rest of it.  There is no protection in the code against that now... better use the mysql version. Unless you add the protection yourself!

       
    • Nobody/Anonymous

      With the text based version, you'll probably loose your data after time. If you have 2 users, or more, accessing the files at the same time. let's say a nth user reads the pistures file while another is writing to it, the nth user will get an incomplete file. When it's time for the nth user to write it back, only the part that was written when he read it will be written back. So you loose the rest of it.  There is no protection in the code against that now... better use the mysql version. Unless you add the protection yourself!

       
    • Nobody/Anonymous

      With the text based version, you'll probably loose your data after time. If you have 2 users, or more, accessing the files at the same time. let's say a nth user reads the pistures file while another is writing to it, the nth user will get an incomplete file. When it's time for the nth user to write it back, only the part that was written when he read it will be written back. So you loose the rest of it.  There is no protection in the code against that now... better use the mysql version. Unless you add the protection yourself!

       

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks