Is "campaign_ $" a bad name for an SQL column?

Question

PostgreSQL allowed me to call the column "campaign_ $". I like the name because it is short and precise, and other potential names like "campaign_receipts" seem longer and less clear.

BUT, interestingly, I will eventually regret marking the $ symbol in the column name, either in PHP or in some other remote part of the architecture. Should I just stick to letters and underscores?

Thank!

Answer 1

Yes you need. "campaign_receipts" is the best name.

Answer 2

You probably won't regret it, but I still don't recommend it.

, ?

, .

Answer 3

, "$" . ? ? ?

Answer 4

, , () , . i18n, , , , .

Answer 5

, , . campaign_money campaign_funds, .

Answer 6

, , , .

/ .. , , .

Answer 7

.

"$" may not be valid in future databases that you use (at some point you can go from PostgreSQL to something else), and it can also create problems at the application level if you do anything that matches column names an object if your programming language does not allow method names to have a "$" in them.

Just my suggestion.