My site contains several forms for users to fill. One of those forms could result in a lot of work. That´s why I´m reaching out for consent. You see, in this form, there will be 40 games. And every game gives the users 2 fields to enter a number (depending on how they think the game will end). So with 40-50 games it means that I have 80-90 fields to keep track of. The two fields will be paired with the right game in the database, and the users answer will be remembered at all time. This is a snap of my code:
<div class="form-left">England- Italy</div>
<div class="form-right"><input type="result" id="g1r1" name="g1r1" class="form-input" /></div>
<div class="form-dash">-</div>
<div class="form-right"><input type="result" id="g1r2" name="g1r2" class="form-input" /></div>
<div class="form-error"></div>
<div class="form-left">Spain- Mexico</div>
<div class="form-right"><input type="result" id="g2r1" name="g2r1" class="form-input" /></div>
<div class="form-dash">-</div>
<div class="form-right"><input type="result" id="g2r2" name="g2r2" class="form-input" /></div>
<div class="form-error"></div>
My thought is, naming the games game1row1 and game1row2. To be able to match them to the correct game in the database. Problem is that an insertion to a table with 90 fields seems hugh. So my question would be: How can this be done in a better way? With less lines of code on the insert-database side..
insert into tablename ( g1r1, g1r2 values 1, 0 where MATCH_ID = MATCHID)
EDIT
To clarify, My table contains ID, user_id, match_id(g), homeScore(r1), awayScore(r2). My idea of g1r1 and g1r2 is to save r1 and r2 at right g(game).