Hmm. This is not the best way to organize a database. You may want to look into normalization. This will cut down on redundacy and maximize efficiency. Also, I can imagine that every time you want to use the data (for example in a CGI script), you are forced to use a split. If you retrieve the normalized data in the first place, you'll probably see a performance boost. That said, what's with the question? SQL has specific keywords that deal with insert and delete. You may look them up in the DBI tutorial.

AgentM Systems nor Nasca Enterprises nor Bone::Easy is responsible for the comments made by AgentM.