Though I typically have used JSON files to store games in the past, I feel like doing this one with a database. It should be more reliable that way, as I find the JSON files often get deleted, and are a bit harder to work with. As part of this work, come up with a data model that will be sufficient for representing an entire game of Root. That sounds like a lot.
Don't worry about accounts or anything, just use the player name/game name pairs like before.
I prefer to use PostgreSQL, and I am most interested in trying SQLx for the driver as it is async and allows using SQL safely without abstracting it behind a Rust API.
Whether the database is accessed from Lumber or if the whole game is pre-loaded, I am not yet sure. Database from Lumber I would be interested to see, but I suspect will be hard, so pre-loaded is totally fine, and probably for the best anyway
Though I typically have used JSON files to store games in the past, I feel like doing this one with a database. It should be more reliable that way, as I find the JSON files often get deleted, and are a bit harder to work with. As part of this work, come up with a data model that will be sufficient for representing an entire game of Root. That sounds like a lot.
Don't worry about accounts or anything, just use the player name/game name pairs like before.
I prefer to use PostgreSQL, and I am most interested in trying SQLx for the driver as it is
asyncand allows using SQL safely without abstracting it behind a Rust API.Whether the database is accessed from Lumber or if the whole game is pre-loaded, I am not yet sure. Database from Lumber I would be interested to see, but I suspect will be hard, so pre-loaded is totally fine, and probably for the best anyway