September 6, 2015 at 8:10 am
Heh... the correct answer is "Just Some Other Notation" that doesn't belong in a database. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2015 at 12:16 am
This was removed by the editor as SPAM
September 7, 2015 at 1:42 am
Easy one, thanks.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
September 7, 2015 at 12:43 pm
A slightly awkward question, I think, since both the third option and the fourth option are correct with the question phrased as it is. Should really be phrased to say "what does JSON stand for" or "what phrase was the acronym JSON coined for".
I suspect that the different wording would have led to well over 90% of answers being correct, instead of only ( 😀 ) 78% (so far).
Tom
September 8, 2015 at 5:22 am
Yes, it was simple. It's at 80% now.
September 8, 2015 at 3:04 pm
I like the first answer best.
September 8, 2015 at 7:30 pm
Iwas Bornready (9/8/2015)
I like the first answer best.
But "JSON" is 5 or 6 letters too short for that, because with those first four words it has to be a truncated JSONTBID (with an optional A between I and D) :hehe:
Tom
September 9, 2015 at 11:47 am
JSON is evil incarnate. XML's bastard sibling at best.
😀
September 9, 2015 at 5:04 pm
Manic Star (9/9/2015)
JSON is evil incarnate. XML's bastard sibling at best.😀
I LOVE IT! A kindred spirit!!!! 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2015 at 7:02 am
Jeff Moden (9/9/2015)
Manic Star (9/9/2015)
JSON is evil incarnate. XML's bastard sibling at best.😀
I LOVE IT! A kindred spirit!!!! 🙂
My first encounter with it was someone sending me a data feed in it. They said it was 'like xml'.
One large powershell script later to read the thing and stuff its contents into a staging database, I was cursing it. Then I had an epiphany, it has 'java' in its name, we all know who pushes Java on the world, and that is the master bastion of evil and decrepitude.
September 11, 2015 at 2:10 pm
Manic Star (9/10/2015)
Jeff Moden (9/9/2015)
Manic Star (9/9/2015)
JSON is evil incarnate. XML's bastard sibling at best.😀
I LOVE IT! A kindred spirit!!!! 🙂
My first encounter with it was someone sending me a data feed in it. They said it was 'like xml'.
One large powershell script later to read the thing and stuff its contents into a staging database, I was cursing it. Then I had an epiphany, it has 'java' in its name, we all know who pushes Java on the world, and that is the master bastion of evil and decrepitude.
Well, there's your problem. You should have used JavaScript, not PowerShell. JavaScript will natively consume JSON. Alternatively, you could have installed SQL 2016 somewhere to parse it. That would probably have taken less time than trying to mangle JSON via PS. 😛
PS. JavaScript has absolutely nothing to to with JAVA (fortunately.)
September 14, 2015 at 2:56 pm
PS 3.0+ automatically converts a json stream to a powershell object. It actually works quite nicely.
Reminds me I need to finish the article I started writing on this.
September 15, 2015 at 6:44 am
sknox (9/11/2015)
Manic Star (9/10/2015)
Jeff Moden (9/9/2015)
Manic Star (9/9/2015)
JSON is evil incarnate. XML's bastard sibling at best.😀
I LOVE IT! A kindred spirit!!!! 🙂
My first encounter with it was someone sending me a data feed in it. They said it was 'like xml'.
One large powershell script later to read the thing and stuff its contents into a staging database, I was cursing it. Then I had an epiphany, it has 'java' in its name, we all know who pushes Java on the world, and that is the master bastion of evil and decrepitude.
Well, there's your problem. You should have used JavaScript, not PowerShell. JavaScript will natively consume JSON. Alternatively, you could have installed SQL 2016 somewhere to parse it. That would probably have taken less time than trying to mangle JSON via PS. 😛
PS. JavaScript has absolutely nothing to to with JAVA (fortunately.)
Whenever possible, I avoid all four. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
September 16, 2015 at 7:52 am
Manic Star (9/10/2015)
Jeff Moden (9/9/2015)
Manic Star (9/9/2015)
JSON is evil incarnate. XML's bastard sibling at best.😀
I LOVE IT! A kindred spirit!!!! 🙂
My first encounter with it was someone sending me a data feed in it. They said it was 'like xml'.
One large powershell script later to read the thing and stuff its contents into a staging database, I was cursing it. Then I had an epiphany, it has 'java' in its name, we all know who pushes Java on the world, and that is the master bastion of evil and decrepitude.
.
JSON is extremely easy to consume in PowerShell. Lets say you have the JSON values in a string variable named $jsonData. You can convert it to a PowerShell object by simply using the convertfrom-json command (https://technet.microsoft.com/en-us/library/hh849898.aspx).
$myObj = ConvertFrom-Json $jsonData
Done...
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply