Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Create moves table #15

Open
brianerdelyi opened this issue Oct 21, 2023 · 0 comments
Open

[Feature Request] Create moves table #15

brianerdelyi opened this issue Oct 21, 2023 · 0 comments

Comments

@brianerdelyi
Copy link

brianerdelyi commented Oct 21, 2023

Currently, each game is stored as a record in the games table. Each record contains a field for each key in the PGN. All moves are stored in moves field. This schema is great for searching games and viewing all moves of a game.

This schema does not enable more advanced analytics of a game such as: position search, centipawn loss evaluation or other analysis based on piece movement. To enable deeper analysis of moves, a table containing all moves is required.

This request is to create a table containing moves for all games. Future feature requests will be created for specific data elements for move analysis.

Request:

  1. Create a new table called moves.
  2. Add each user's move (i.e. ply) to the moves table. Suggested fields include:
    GameID (Key for the game in the games table) *
    Ply (Ply number)
    Move (Move number)
    Player (Player name)
    Color (Colour)
    Piece (Piece moved by user)
    Notation (Move notation)
    Clock (Time left on the clock h:mm:ss)
    Move_Time (Time used for the move in seconds)
    FEN (FEN of the position after the user's move) **

Note *: I do not believe the games table includes a key for GameID. This will need to exist in the games table as well.
Note **: FEN be the basis for future feature requests that involve engine evaluations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant