No. You need to list your columns out, and remove the one you don't want. If you really don't want to write them all out, purchase a add-on tool that allows the * character to be expanded by a hot key (for example, I use SQL Prompt, and you can Tab the * to have to changed to the name of every column with their relevant object prefix (alias)), and then remove the "offending" column.
This sounds like an interesting addition to the SQL syntax but it's always better to be explicit in what you are returning as opposed to implicit. Imaging expecting a result set containing 10 columns (which the id column was excluded from) and then months later someone added 5 more columns to the table. Is your code robust enough to deal with the unexpected columns? Would anyone else's code that consume's the result set be?
*
character to be expanded by a hot key (for example, I use SQL Prompt, and you canTab
the*
to have to changed to the name of every column with their relevant object prefix (alias)), and then remove the "offending" column.SELECT *
in any format is bad practice.WHILE
solution on the duplicate.id
column was excluded from) and then months later someone added 5 more columns to the table. Is your code robust enough to deal with the unexpected columns? Would anyone else's code that consume's the result set be?