@Dodi82 If you're unexpectedly getting comparison between string and char, be aware that strings are implicitly convertible to char[] (char arrays) so if you have a misplaced index operator somewhere, like string1 == string2[0] this could be the source of that problem.
That's what they mean by legacy that'll bite you in the ass down the road. I could see saying "what the hell is this supposed to do" and reverting it to SELECT TOP 100 PERCENT .
Use a CASE statement and one single SELECT.
INSERT INTO NEW_TABLE
SELECT CASE WHEN CONDITION1 THEN COL1
WHEN CONDITION2 THEN COL2
ELSE COL3
END
FROM SOURCE_TABLE;
The problem is if we give it a cool name people will want to go there. And it'll draw attention to a room that's really supposed to stay out of the consciousness.
We are discontinuing Blog Overflow as a service on this network. Not only does this mean that no new blogs will be created, but it will also mean that all extant blogs are becoming functionally shut down.
The reasoning is three-fold in basic:
The vast majority of blogs aren't really active. Th...
Use a CASE statement and one single SELECT.
INSERT INTO NEW_TABLE
SELECT CASE WHEN CONDITION1 THEN COL1
WHEN CONDITION2 THEN COL2
ELSE COL3
END
FROM SOURCE_TABLE;
We are discontinuing Blog Overflow as a service on this network. Not only does this mean that no new blogs will be created, but it will also mean that all extant blogs are becoming functionally shut down.
The reasoning is three-fold in basic:
The vast majority of blogs aren't really active. Th...
