Change Details

SecurePoll's database schema includes a field `el_owner` defined as a non-null integer with no default value. In practice, it is never assigned a value by the poll creation page either. Running `grep owner * -r` on the code indicates it is never used anywhere really. In practice, it is always assigned the value 0. It should instead be populated with the user ID of the user who creates the poll.

SecurePoll's database schema includes a field `el_owner` defined as a non-null integer with no default value. In practice, it is never assigned a value by the poll creation page either. Running `grep owner * -r` on the code indicates it is never used anywhere really. In practice, it is always assigned the value 0 if the database is not using strict mode. If the DB is using strict mode, CreatePage will throw a DB exception because `el_owner` doesn't have a default value; this means you cannot even create a poll in strict mode. The `el_owner` field should instead be populated with the user ID of the user who creates the poll. That way we won't have issues with strict mode either.

SecurePoll's database schema includes a field `el_owner` defined as a non-null integer with no default value. In practice, it is never assigned a value by the poll creation page either. Running `grep owner * -r` on the code indicates it is never used anywhere really. In practice, it is always assigned the value 0 if the database is not using strict mode. If the DB is using strict mode, CreatePage will throw a DB exception because `el_owner` doesn't have a default value; this means you cannot even create a poll in strict mode. ItThe `el_owner` field should instead be populated with the user ID of the user who creates the poll. That way we won't have issues with strict mode either.