It's not really a problem, I'm just going through the process of filling in all the holes in my MySQL knowledge - and this issue seems like it could be a timesaver. I designed this table to contain two types of fields, "user info" (prefix: F_user) and "user prefs" (prefix: F_pref) so that I could single out all F_pref_ fields with pattern matching or something. I wanted to avoid having a separate table to contain data that only paired one to one with data in another table.
I understand that not explicitly entering column names has been called a security risk. I.E. if you add a column to a table that contains sensitive data and shouldn't be called unless necessary - then SELECT * from table may make that new sensitive data available where such broad SELECT statements are used, especially in this case where the rest of the table contains user data.
Since this project is still in development, I have been adding F_pref_ columns as necessary, and I wanted to avoid having to type them in explicitly wherever the occur in my scripts.
I dunno, maybe making a separate table is necessary here...
Thanks.