Importing other data implies a whole new set of conditions (and a rather large set). For example, "Bought-in time" isn't exactly the same thing as "how many chips the player has". In fact, it's only one piece of a larger set of data. "Bought-in time" is the timestamp on a player's buy-in, and you can't import that without importing all of the other data about the buy-in, such as the profile, cost, rake(s), chips, bounty chip, etc. Importing each of those has even more implications, and a lot of error-checking and data integrity checking that would have to accompany it. Likewise, "Still in" isn't really even a value that a player is assigned, but rather just the description of the state of the player. What I mean is there's no field on an internal player object that says whether or not the player is "still in". The player is "still in" if he/she has a buy-in and doesn't have a corresponding bust-out AND the tournament is still going. Importing any of these would clearly imply being able to import rebuys and add-ons, which have their own requirements and implications. This isn't a just tall order, it's a pretty huge one, and I'm not sure how valuable the payoff would be. What is it you're trying to do?
When I export a CSV file, I get all the options and data to export.
It's different when importing.
If for example I export the chipcount so that I can merge two day1 into day2, when importing, I can import the chipcount, but not the "player has bought in": so I have to buy-in players and the chipcount is lost.
I'm not sure I'm following you. CSV files, by definition, have multiple columns, each separated by a comma.
Yes, but as you said, each columns are separated by a comma, while in an excel file, each columns are separated without any commas
It would be perfect like this because in this way I can import a more easy to write file
Show Posts
