Sfrgttk

What do the Banks children have against barley water?

What is the motivation for a law requiring 2 parties to consent for recording a conversation

Is an up-to-date browser secure on an out-of-date OS?

Is three citations per paragraph excessive for undergraduate research paper?

Where to refill my bottle in India?

Adding labels to a table: columns and rows

Should I use my personal or workplace e-mail when registering to external websites for work purpose?

What is the best strategy for white in this position?

What is this 4-propeller plane?

How is radar separation assured between primary and secondary targets?

Protecting Dualbooting Windows from dangerous code (like rm -rf)

Does a dangling wire really electrocute me if I'm standing in water?

Inversion Puzzle

Deadlock Graph and Interpretation, solution to avoid

Is "plugging out" electronic devices an American expression?

On the insanity of kings as an argument against monarchy

Spanish for "widget"

Idiomatic way to prevent slicing?

What do hard-Brexiteers want with respect to the Irish border?

What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?

Extreme, unacceptable situation and I can't attend work tomorrow morning

Why can Shazam fly?

I see my dog run

What is the steepest angle that a canal can be traversable without locks?

Must numeric JSON keys be quoted?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

0

I've noted that key-value values may be unquoted, when numeric, in TSQL JSON strings but it seems the key component must always be quoted.

select 1, isjson(''), 'empty string' union

select 2, isjson('{}'), 'empty braces' union

select 3, isjson('{1:2}'), 'unquoted both, numerals both' union

select 4, isjson('{1:"2"}'), 'unquoted key, numerals both' union

select 5, isjson('{"1":2}'), 'unquoted value, numerals both' union

select 6, isjson('{"1":"2"}'), 'quoted both, numerals both' union

select 7, isjson('{a:b}'), 'unquoted both, alpha both' union

select 8, isjson('{a:"b"}'), 'unquoted key, alpha both' union

select 9, isjson('{"a":b}'), 'unquoted value, alpha both' union

select 10, isjson('{"a":"b"}'), 'quoted both, alpha both'

order by 1

;

The above demonstrates this but my questions are:

1. Must this always be so? (Is there a configuration that can override this behaviour?)


2. Is this behaviour specified by JSON or SQL Server?


3. What is the rationale behind this design decision?


4. Would there be a performance benefit if SQL Server automatically cast unquoted numerals as integers?

sql-server t-sql json

share

asked 1 min ago

youcantryreachingmeyoucantryreachingme

4417

add a comment | 

0

I've noted that key-value values may be unquoted, when numeric, in TSQL JSON strings but it seems the key component must always be quoted.

select 1, isjson(''), 'empty string' union

select 2, isjson('{}'), 'empty braces' union

select 3, isjson('{1:2}'), 'unquoted both, numerals both' union

select 4, isjson('{1:"2"}'), 'unquoted key, numerals both' union

select 5, isjson('{"1":2}'), 'unquoted value, numerals both' union

select 6, isjson('{"1":"2"}'), 'quoted both, numerals both' union

select 7, isjson('{a:b}'), 'unquoted both, alpha both' union

select 8, isjson('{a:"b"}'), 'unquoted key, alpha both' union

select 9, isjson('{"a":b}'), 'unquoted value, alpha both' union

select 10, isjson('{"a":"b"}'), 'quoted both, alpha both'

order by 1

;

The above demonstrates this but my questions are:

1. Must this always be so? (Is there a configuration that can override this behaviour?)


2. Is this behaviour specified by JSON or SQL Server?


3. What is the rationale behind this design decision?


4. Would there be a performance benefit if SQL Server automatically cast unquoted numerals as integers?

sql-server t-sql json

share

asked 1 min ago

youcantryreachingmeyoucantryreachingme

4417

add a comment | 

I've noted that key-value values may be unquoted, when numeric, in TSQL JSON strings but it seems the key component must always be quoted.

select 1, isjson(''), 'empty string' union

select 2, isjson('{}'), 'empty braces' union

select 3, isjson('{1:2}'), 'unquoted both, numerals both' union

select 4, isjson('{1:"2"}'), 'unquoted key, numerals both' union

select 5, isjson('{"1":2}'), 'unquoted value, numerals both' union

select 6, isjson('{"1":"2"}'), 'quoted both, numerals both' union

select 7, isjson('{a:b}'), 'unquoted both, alpha both' union

select 8, isjson('{a:"b"}'), 'unquoted key, alpha both' union

select 9, isjson('{"a":b}'), 'unquoted value, alpha both' union

select 10, isjson('{"a":"b"}'), 'quoted both, alpha both'

order by 1

;

The above demonstrates this but my questions are:

1. Must this always be so? (Is there a configuration that can override this behaviour?)


2. Is this behaviour specified by JSON or SQL Server?


3. What is the rationale behind this design decision?


4. Would there be a performance benefit if SQL Server automatically cast unquoted numerals as integers?

sql-server t-sql json

share

asked 1 min ago

youcantryreachingmeyoucantryreachingme

4417

select 1, isjson(''), 'empty string' union

select 2, isjson('{}'), 'empty braces' union

select 3, isjson('{1:2}'), 'unquoted both, numerals both' union

select 4, isjson('{1:"2"}'), 'unquoted key, numerals both' union

select 5, isjson('{"1":2}'), 'unquoted value, numerals both' union

select 6, isjson('{"1":"2"}'), 'quoted both, numerals both' union

select 7, isjson('{a:b}'), 'unquoted both, alpha both' union

select 8, isjson('{a:"b"}'), 'unquoted key, alpha both' union

select 9, isjson('{"a":b}'), 'unquoted value, alpha both' union

select 10, isjson('{"a":"b"}'), 'quoted both, alpha both'

order by 1

;

share

asked 1 min ago

youcantryreachingmeyoucantryreachingme

4417

share

asked 1 min ago

youcantryreachingmeyoucantryreachingme

4417

asked 1 min ago

youcantryreachingmeyoucantryreachingme

4417

asked 1 min ago

youcantryreachingmeyoucantryreachingme

4417