We are doing a reader survey, and many of the questions involve multiple selection answers (in this case, we're using check boxes). So of course, answers are arrays, and are then stored in mysql after being serialized.

My problem is arising when trying to get the collected info out in a readable format. I would like to spit out each distinct value and then a count of how many readers checked it.

For example, with a single select question, I'm doing it this way with no problem:

PHP Code:

<? $resAge = mysql_query("select age, count(*) as numAge from survey2010 group by age");
                            
while ($rowAge = mysql_fetch_array($resAge)){
    extract($rowAge);
    $perAge = round(($numAge / $respondants) *100, 0);
    print('<tr><td class="surveyForm"> ' .$age .'</td><td class="surveyForm">' .$numAge .'</td><td class="surveyForm">' .$perAge .'% </td></tr>');
        }
?>

I'm completely baffled on how to make this work with the above described situation in which each row from mysql is possibly an array itself. Suggestions would be very much appreciated. Thanks.

What's the definition of survey2010?

Originally Posted by PaulW

What's the definition of survey2010?

survey2010 is the name of the mysql table

So of course, answers are arrays, and are then stored in mysql after being serialized.

This is a bad answer... you should use another related mysql table, with your answers.

As you know, mysql doesn't unserialize... so you have to make all with PHP

make a select with all fields {
make unserialize and create another array like, $arr[$age][] = answers
to count and do whatever you like BUT...
}

it takes almost double time, because you could do this only from mysql if you had a good database structure

First, you don't want to use print but rater echo, echo is both faster and more stable then print.

As far as the code goes try the post above me but remember that echo is better to code with. and always use the full <?php in the start of your code to make sure it will work with all php versions and servers set up differently.

Interestingly enough, that's how I've done similar things in the past - with multiple tables. But at some point, I feel like someone told me it was a really clumsy, inefficient way to do things.. hence this. Perhaps I need to reconsider.

Originally Posted by anthonyrossbach

First, you don't want to use print but rater echo, echo is both faster and more stable then print.

As far as the code goes try the post above me but remember that echo is better to code with. and always use the full <?php in the start of your code to make sure it will work with all php versions and servers set up differently.

thanks for the advice

Originally Posted by anthonyrossbach

First, you don't want to use print but rater echo, echo is both faster and more stable then print.

The performance difference is negligible. What do you mean by echo is more stable?. If anything print is more stable considering that there is a special case where print will work and echo won't.

Originally Posted by anthonyrossbach

and always use the full <?php in the start of your code to make sure it will work with all php versions and servers set up differently.

This is absolutely true. Using short tags in place of the php tag is the best way to kill the portability of your code.

I reworked this to use separate tables for each multiple-select question. Much easier.

thanks for all the help.

Nice you got it working, having separate tables sometimes is the easiest solution