Why do you need this? Without knowing the answer to this question, I'll go ahead and simply suggest that you don't.
Are you aware that you'd be breaking 1NF by doing this (see database normalization
Instead, create your member table with an auto incrementing id field and region id as a foreign key, each stored separately and in a non-related fashion. That is
-- table to store regions
CREATE TABLE region (
id INT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
name VARCHAR(20)
)
-- table to store members
CREATE TABLE member (
id INT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
region_id INT UNSIGNED,
-- and of course, other stuff goes in this table as well, such as
name VARCHAR(30),
FOREIGN KEY (region_id) REFERENCES region(id)
)
Looking up members by region is now easy
-- by region id
SELECT id, name FROM member WHERE region_id=212;
-- by region name
SELECT m.id, m.name
FROM member m
INNER JOIN region r ON m.region_id = r.id
WHERE r.name = 'some_area';
And counting number of members in an area is also done just as easily
SELECT COUNT(*), r.name
FROM member m
INNER JOIN region r ON r.id = m.region_id
GROUP BY r.name;