August 8, 2022 at 8:51 pm
- Add wizard for PIVOT, like one in MS Access
- Expand list of Boolean operators, add implication => and equivalence <=>. It is cumbersome and confusing writing NOT P OR Q instead P=>Q. For equivalence it is (NOT P OR Q ) AND (NOT Q OR P). Maybe people would use tem in CHECK constraints.
Zidar's Theorem: The best code is no code at all...
August 15, 2022 at 1:02 pm
Of course, if the SQL Server team actually implemented any of these suggestions, they would be making T-SQL even more proprietary. Maybe we should be directing to these requests to the ANSI SQL committee - if such a group exists at the moment.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
August 15, 2022 at 2:32 pm
I want intellisense to work consistently.....
And when there's a column overflow/truncation the error message should include the freaking column name.....
BCP supporting database to database transfer so I don't have to do some janky dump to a temp file then import.
August 15, 2022 at 8:53 pm
client tools are always tough.
Column truncation has gotten better with 2019.
bcp is unlikeley to go db to db, but it would be nice.
Viewing 4 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply