@telltaleatheist I just watched https://t.co/0UES5Irbug and I realize it's over a year old, but just in case you haven't come across this info: "Urim and Tummim" are a thing, but as you said, that doesn't prove anything (it actually raises more questions) https://t.co/OrdgIIB0Ph
@ChipotleTweets Oh, thanks. Sorry I didn't see this before adding the other 2. I looked on the site for a contact form before submitting here but couldn't find anything. Should I delete my request tweets?
@ChipotleTweets App Request #2: Please consider adding a small text field for "Special Instructions", or something along those lines, to pass a short "note" to those who will be preparing the order. Thanks!
@ChipotleTweets App Request #3: Please consider storing in-progress order on server instead of local device, allowing for collaboration. I start order for myself + kid #1. My wife, who is somewhere else, adds hers plus kids 2 and 3. Either one of us can finish/pay and pick up. 😺
@ChipotleTweets App Request #1: For kids meals, instead of "ADD RICE" and "ADD BEANS", have "SIDE #1" and "SIDE #2", each one with options for both types of rice and beans. My kids want double rice and no beans but can't order it through the app. Thanks!
Please support (i.e. vote for) this most humble and reasonable suggestion for the betterment of #SupplementaryCharacters (ok, fine, #emojis 😸 , are you happy?) in SQL Server 😺 @SQLServer @sergten @SQLPedro @BrentO https://t.co/Kg3U0L9Jhc
¡¡Hear ye, hear ye⦂ On December 7ᵗʰ @ 2:30 PM I'll be presenting ❝#ModuleSigning: Use #Certificates to Replace #TRUSTWORTHY, EXECUTE AS, and Cross-DB Pwnership Chaining❞ at #SQLSaturday918 in Charlotte, NC‼ Come check it out 💥 #SQLSatCLT @SQLSwimmer https://t.co/jCbYGRQ5bw
Please support my suggestion to have Microsoft add the two missing object types to the otherwise wonderful-even-if-undocumented "SQLSERVR -Q" method of globally updating collations on an instance: https://t.co/8tX5q3ACQ8
@way0utwest In general no, but there are several caveats / nuances. If you post this as a question to either https://t.co/ceyzwmreYc or https://t.co/1SJ3ONBty2 then I (@SqlQuantumLeap) can give a proper answer. The other responses you received here are mostly incorrect.
Please vote for my latest enhancement request suggestion idea: ❝Support standard escape sequences in strings (e.g. unescape "\t" into CHAR(9), "\n" into CHAR(10), etc)❞ #Unicode#EscapeSequence#SQLServer @SQLPedro @sergten @SQLServer https://t.co/gueBbDpuRD
My updates to the escape sequences info on the #Dotnet#CSharp "Strings" page are live. For #Unicode sequences I added/fixed: format, range, and an example. Added warning re: "\x" with < 4 digits. Escape sequence info is now fully informative! 😎 @docsmsft https://t.co/gb8hrJgmXd
My updates to the escape sequences info on the #FSharp "Strings" page are now live. Added 5 missing sequences! For each #Unicode sequence I added: format, range, and an example. Escape sequence info is now both complete *and* informative! 😎 https://t.co/pEjZzRyds9
@DavidJPoole @andrewsduncan1 Sad that there are those who can't grasp the basic concept of *EQUAL* such that this is even a question 😾, nor the irony that if there is a double-standard, they are the source of it.
FYI: I updated the following documentation so that, for the first time since the release of #SQLServer 2012, the pages for https://t.co/lo9fbJxmTU , https://t.co/Agmkv4YFL7 , and https://t.co/OAKMfgtuNE are correct / complete (or darn close 😺 ) 😎 ( https://t.co/nbyhdNt07b )
FYI for anyone in the Raleigh / Durham / RTP area: I will be presenting "#ModuleSigning or: How I Learned to Stop Using #TRUSTWORTHY / EXECUTE AS and Love Certificates" this Saturday, 2019-04-27, at #sqlsatraleigh#SQLServer https://t.co/xydYuq2GD3 @SQLSatRaleigh
#sqlsatraleigh is this weekend. You can still sign up at https://t.co/ZNMwgneZJC.
The paper bag I'm breathing into for the next three days is just recreational...