Thank you for welcome and reply
I will be adding new positions regularly and maybe new themes will show up. What i was thinking about con for MySQL was this:
Say I make table with primary key FEN code. FEN code is
string wich uniquely identifies a chess position. Now i have to make 1 column for each theme so when creating database will have to fix number of themes eg the following could be the table:
FEN code | Error size | Theme 1 | Theme 2 | ..... | Theme n |
Addded: Forgot to ask something about XML: What would be "best" you: The FEN code seems like natural primary key in relational database but in the XML would you prefer just this cryptic FEN string or a more verbose human friendly description of the chess position ? One could simple somehow create XML tags for each board element and then have XML elements for the different chess pieces.