The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Of those, I use only SQL, and it's worse than that. (Transact-SQL at least.)
Remember that RTRIM and LTRIM remove only SPACEs, not all whitespace.
Basically, LEN (and RTRIM and LTRIM) work on bytes, so it does the same things with VARBINARY as it does with VARCHAR.
So I should not have been surprised when performing LEN on a VARBINARY ignores 0x32 at the end as well.
This is my fave thing to do in a query window for a quick update:
BEGINBEGINTRANUPDATE [SomeTable] SET [someColumn] = 'someNewValue'WHERE [someID] = 0ROLLBACKCOMMITEND
I still get intellisense within the BEING/END area and, should I accidentally press F5 or run the silly thing w/o selecting the code to run, no harm done.
Yeah, I know, gotta make sure I include the WHERE clause, and also BEGIN TRAN. I then select and run COMMIT.
The best way to improve Windows is run it on a Mac.
The best way to bring a Mac to its knees is to run Windows on it.
~ my brother Jeff
I remember being frustrated by the fact C# 1.0 had a default container called ArrayList. Is it an Array, or a List? These are very different things. Is it a fancy container that somehow has worked out how to get the benefits of both? The documentation never said.
Of course, there also were well designed CPUs[^] that had exactly 256 opcodes, with only 0x68 being reserved as prefix for future expansions of the instruction set. And of course there are the opcodes 0xE0 - 0xEF, the 'Set X Register' instruction for registers 0x0 - 0xF, short SEX. Absolutely no confusion here.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.