I need to establish, as part of a client registration process, a table containing a series of arrays with default values. Previously, this was done with 'C', the default values forming strings which in the 'C' world, are null-terminated arrays by definition.
Typically, we would need to establish an array of test sections which would include arrays of responses, arrays of raw scores and arrays of standard scores, all of sizes which vary from test section to test section.
I can accomplish this through a call to an include function, making use of mysqli prepared statements. All user input to the response arrays is via radio button selection so making use of enum typing appears to be redundant.
This seems to be the way to go in order to establish new table rows on demand, and to make it straightforward to later compare responses against a scoring template (which would be built the same way), thereby populating the raw score array when all responses have been posted.
While more involved to setup than simple strings in old isam files, this method appeals to me as offering best data management all around.
So .... before I blindly dig a deep, dark hole for myself, could some more experienced players out there assure me I am not proposing something rash or illogical?
Thanks so much for taking the time to have a look at this.
