登录表单，选择名称选项值

Question

I have three tables currently setup. I want when somebody signs in, they choose 1 of the options in the select dropdown and it goes into that separate database.

Eg Favourite color

<select name="color">
        <option value="Red">Red</option>
        <option value="Blue">Blue</option>
        <option value="White">White</option>
        </select> 

All reds picked, go into the red database, all blue into the blue database etc etc.

Thanks

Answer 1

What you are trying to do is separate your data by a specific value. This is a pretty normal thing to do, but you are trying to go about it all wrong. There is nearly never a good reason to have a variable table name - instead, you should use columns to separate this data.

The proper solution:

A better way to handle the situation is to create a single table (EG colors , with a column of color which you can assign the variable that was selected.

EG:

$query = "INSERT INTO colors (color) VALUES (?)";

Where the question mark is the variable in question (In a prepared statement).

This way all of your variables are in a single table but still separated by the color the user chose and can be sorted as such.

---

To answer your question:

If you wish to ignore my multiple warnings above that you are going about this the wrong way (You are your own person after all and can make decisions for yourself), here is how you can do this the way you are asking (But again, I really really really really do NOT recommend this method).

If you do this, you should check to make sure that the option that was selected matches a list of possible selections:

$possible = ["Red", "Blue", "White"];

if(in_array($_POST['color'], $possible)) {
    $query = "INSERT INTO {$_POST['color']} ...";
}

Doing it this way will prevent SQL Injection via the variable that is being concatenated into the string.

If you just insert the users variable without checking it first, the user can change the actual value of the drop-down on the client side, which could easily put your application at risk.

NOTE : I do not recommend doing it this way - it's harder to upkeep and it isn't the proper way to do such a thing.