Quote:
Originally Posted by yash101
So, with this data storage, are you using text-based database? If so:
match/team#/climb code (0=no,1=10,2=20,3=30)
That would be a lot more readable to PHP and easier to implement. However, it would be important to note that text-based isn't so reliable. If this software is running for multiple teams, every time a match ends, the server will get a huge load. Multiple appends to the same file at the same time, many times, means a corrupt file. Instead, MySQL or some other database server built to store information may be the lifesaver!
The only time I used text databases is when I was learning PHP and using it on a site that maxes out at a view per day! |
I was suggesting it as an interchange format. Think of it as an alternative to sending around the output of "mysqdump".
I feel like I'm missing something because I don't understand your suggested format at all:
- Is splitting text apart with a slash is easier than a space? It's been a while since I've written any PHP but why would slash be any different?
- Why have you chosen to omit the column name? Without it you have to add meta-data someplace else to describe what it is.
- How is representing climbs as 0-3 better than 0/10/20/30? They seem the same to me.
I also don't see why any of this would be a lot of work on the server.