As an addition to what was already suggested, I'd suggest this for your database design:

You have a main table that stores your base information and a secondary table that stores the selected checkboxes.

This might take a little longer to set up, but will save you some time and headache in the future.

main table
+------------------+
| Field            |
+------------------+
| id               |
| column_1         |
+------------------+

secondary table
+------------------+
| Field            |
+------------------+
| id               |
| main_table_id    |
| checkbox         |
+------------------+
[download]

This, of course, is a basic example and there are other ways to accomplish what you are trying to do. The question guiding your decision should be:

Do I anticipate this application to grow? If so, how much and how fast? Either way, it is always good practice to plan for growth.

Also, if you're not using it already, take a look at Class::DBI.