Menu
Feb 04, 2020 Commands/tellraw. From Minecraft Wiki Arguments player Specifies the player(s) to send the message to. Must be a player name or target selector. Raw json message. Cross-platform.NET sample microservices and container based application that runs on Linux Windows and macOS. Powered by.NET Core 3.0, Docker Containers and Azure Kubernetes Services. Supports Visual Studio, VS for Mac and CLI based environments with Docker CLI, dotnet CLI, VS Code or any other code editor.
Json.NET is a popular high-performance JSON framework for .NET
There is a newer version of this package available.
See the version list below for details.
See the version list below for details.
Requires NuGet 2.12 or higher.
For projects that support PackageReference, copy this XML node into the project file to reference the package.
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
Dependencies
.NETFramework 2.0
- No dependencies.
.NETFramework 3.5
- No dependencies.
.NETFramework 4.0
- No dependencies.
.NETFramework 4.5
- No dependencies.
.NETStandard 1.0
- Microsoft.CSharp(>= 4.3.0)
- NETStandard.Library(>= 1.6.1)
- System.ComponentModel.TypeConverter(>= 4.3.0)
- System.Runtime.Serialization.Primitives(>= 4.3.0)
.NETStandard 1.3
- Microsoft.CSharp(>= 4.3.0)
- NETStandard.Library(>= 1.6.1)
- System.ComponentModel.TypeConverter(>= 4.3.0)
- System.Runtime.Serialization.Formatters(>= 4.3.0)
- System.Runtime.Serialization.Primitives(>= 4.3.0)
- System.Xml.XmlDocument(>= 4.3.0)
.NETStandard 2.0
- No dependencies.
Portable Class Library (.NETFramework 4.0, Silverlight 5.0, Windows 8.0, WindowsPhone 8.0, WindowsPhoneApp 8.1)
- No dependencies.
Portable Class Library (.NETFramework 4.5, Windows 8.0, WindowsPhone 8.0, WindowsPhoneApp 8.1)
- No dependencies.
GitHub Usage
Showing the top 10 GitHub repositories that depend on Newtonsoft.Json:
Repository | Stars |
---|---|
shadowsocks/shadowsocks-windows If you want to keep a secret, you must also hide it from yourself. | |
CodeHubApp/CodeHub CodeHub is an iOS application written using Xamarin | |
PowerShell/PowerShell | |
Wox-launcher/Wox Launcher for Windows, an alternative to Alfred and Launchy. | |
0xd4d/dnSpy | |
dotnet-architecture/eShopOnContainers Cross-platform .NET sample microservices and container based application that runs on Linux Windows and macOS. Powered by .NET Core 3.0, Docker Containers and Azure Kubernetes Services. Supports Visual Studio, VS for Mac and CLI based environments with Docker CLI, dotnet CLI, VS Code or any other code editor. | |
dotnet/roslyn The Roslyn .NET compiler provides C# and Visual Basic languages with rich code analysis APIs. | |
ShareX/ShareX ShareX is a free and open source program that lets you capture or record any area of your screen and share it with a single press of a key. It also allows uploading images, text or other types of files to many supported destinations you can choose from. | |
mono/mono Mono open source ECMA CLI, C# and .NET implementation. | |
MaterialDesignInXAML/MaterialDesignInXamlToolkit Google's Material Design in XAML & WPF, for C# & VB.Net. |
Read more about the GitHub Usage information on our documentation.
Version History
Version | Downloads | Last updated |
---|---|---|
12.0.3 | 9,763,998 | 11/9/2019 |
12.0.2 | 33,594,983 | 4/22/2019 |
12.0.1 | 32,112,709 | 11/27/2018 |
11.0.2 | 36,795,139 | 3/24/2018 |
11.0.1 | 21,578,832 | 2/17/2018 |
10.0.3 | 65,042,702 | 6/18/2017 |
10.0.2 | 33,072,222 | 4/2/2017 |
10.0.1 | 34,444,257 | 3/20/2017 |
9.0.1 | 43,328,460 | 6/22/2016 |
8.0.3 | 10,130,686 | 3/14/2016 |
8.0.2 | 4,426,869 | 1/9/2016 |
8.0.1 | 1,380,478 | 12/29/2015 |
7.0.1 | 13,547,539 | 6/22/2015 |
6.0.8 | 15,981,791 | 1/11/2015 |
6.0.7 | 796,473 | 12/23/2014 |
6.0.6 | 4,728,639 | 10/24/2014 |
6.0.5 | 3,078,349 | 9/6/2014 |
6.0.4 | 19,435,134 | 8/3/2014 |
6.0.3 | 2,309,425 | 4/27/2014 |
6.0.2 | 869,120 | 3/30/2014 |
6.0.1 | 2,609,562 | 2/1/2014 |
5.0.8 | 3,152,052 | 10/17/2013 |
5.0.7 | 471,707 | 10/14/2013 |
5.0.6 | 3,018,647 | 6/6/2013 |
5.0.5 | 563,190 | 5/8/2013 |
5.0.4 | 1,924,765 | 4/25/2013 |
5.0.3 | 313,168 | 4/14/2013 |
5.0.2 | 270,571 | 4/8/2013 |
5.0.1 | 1,695,731 | 4/7/2013 |
4.5.11 | 7,730,751 | 11/20/2012 |
4.5.10 | 335,886 | 10/7/2012 |
4.5.9 | 217,333 | 9/8/2012 |
4.5.8 | 252,685 | 8/4/2012 |
4.5.7 | 285,687 | 6/9/2012 |
4.5.6 | 1,960,039 | 5/30/2012 |
4.5.5 | 75,191 | 5/8/2012 |
4.5.4 | 74,357 | 4/24/2012 |
4.5.3 | 32,529 | 4/13/2012 |
4.5.2 | 20,214 | 4/11/2012 |
4.5.1 | 349,150 | 3/20/2012 |
4.0.8 | 263,691 | 2/12/2012 |
4.0.7 | 269,915 | 1/24/2012 |
4.0.6 | 19,551 | 1/23/2012 |
4.0.5 | 146,420 | 12/10/2011 |
4.0.4 | 36,083 | 11/19/2011 |
4.0.3 | 58,378 | 10/2/2011 |
4.0.2 | 73,380 | 4/23/2011 |
4.0.1 | 107,976 | 4/22/2011 |
3.5.8 | 392,082 | 1/8/2011 |
Note:
The JSON_TABLE
function is available starting with Oracle Database 12c Release 1 (12.1.0.2).Syntax
Description of the illustration 'json_table.gif'
(JSON_path_expression::=, JSON_table_on_error_clause::=, JSON_columns_clause::=)
JSON_path_expression::=
Description of the illustration 'json_path_expression.gif'
object_step::=
Description of the illustration 'object_step.gif'
array_step::=
Description of the illustration 'array_step.gif'
JSON_table_on_error_clause::=
Description of the illustration 'json_table_on_error_clause.gif'
JSON_columns_clause::=
Description of the illustration 'json_columns_clause.gif'
Dxo photo software suite 03.2017 download. JSON_column_definition::=
Description of the illustration 'json_column_definition.gif'
JSON_exists_column::=
Description of the illustration 'json_exists_column.gif'
(The syntax and semantics of these clauses are described in the
JSON_EXISTS
and JSON_VALUE
documentation: JSON_value_return_type::=, JSON_path_expression::=, JSON_exists_on_error_clause::=)JSON_query_column::=
Description of the illustration 'json_query_column.gif'
(The syntax and semantics of these clauses are described in the
JSON_QUERY
documentation: JSON_query_return_type::=, JSON_query_wrapper_clause::=, JSON_path_expression::=, JSON_query_on_error_clause::=)JSON_value_column::=
Description of the illustration 'json_value_column.gif'
(The syntax and semantics of these clauses are described in the
JSON_VALUE
documentation: JSON_value_return_type::=, JSON_path_expression::=, JSON_value_on_error_clause::=)JSON_nested_path::=
Description of the illustration 'json_nested_path.gif'
(JSON_path_expression::=, JSON_columns_clause::=)
ordinality_column::=
Description of the illustration 'ordinality_column.gif'
Purpose
JSON_TABLE
creates a relational view of JSON data. It maps the result of a JSON data evaluation into relational rows and columns. You can query the result returned by the function as a virtual relational table using SQL. The main purpose of JSON_TABLE
is to create a row of relational data for each object inside a JSON array and output JSON values from within that object as individual SQL column values.You can specify
JSON_TABLE
only in the FROM
clause of a SELECT
statement. The function first applies a JSON path expression, called a rowpathexpression, to the supplied JSON data. The JSON value that matches the row path expression is called a rowsource in that it generates a row of relational data. The COLUMNS
clause evaluates the row source, finds specific JSON values within the row source, and returns those JSON values as SQL values in individual columns of a row of relational data.The
COLUMNS
clause enables you to search for JSON values in different ways by using the following clauses:JSON_exists_column
- Evaluates JSON data in the same manner as theJSON_EXISTS
condition, that is, determines if a specified JSON value exists, and returns either aVARCHAR2
column of values 'true
' or 'false
', or aNUMBER
column of values 1 or 0.JSON_query_column
- Evaluates JSON data in the same manner as theJSON_QUERY
function, that is, finds one or more specified JSON values, and returns a column of character strings that contain those JSON values.JSON_value_column
- Evaluates JSON data in the same manner as theJSON_VALUE
function, that is, finds a specified scalar JSON value, and returns a column of those JSON values as SQL values.JSON_nested_path
- Allows you to flatten JSON values in a nested JSON object or JSON array into individual columns in a single row along with JSON values from the parent object or array. You can use this clause recursively to project data from multiple layers of nested objects or arrays into a single row.ordinality_column
- Returns a column of generated row numbers.
The column definition clauses allow you to specify a name for each column of data that they return. You can reference these column names elsewhere in the
SELECT
statement, such as in the SELECT
list and the WHERE
clause.expr
Use this clause to specify the JSON data to be evaluated. For
expr
, specify an expression that evaluates to a text literal. If expr
is a column, then the column must be of data type VARCHAR2
, CLOB
, or BLOB
. If expr
is null, then the function returns null.If
expr
is not a text literal of well-formed JSON data using strict or lax syntax, then the function returns null by default. You can use the JSON_table_on_error_clause
to override this default behavior. Refer to JSON_table_on_error_clause.FORMAT JSON
You must specify
FORMAT
JSON
if expr
is a column of data type BLOB
.JSON_path_expression
Use this clause to specify the row path expression. The function uses the row path expression to evaluate
expr
and find the a JSON value, called the row source, that matches, or satisfy, the path expression. This row source is then evaluated by the COLUMNS
clause. The path expression must be a text literal.The
JSON_path_expression
clause has the same semantics for JSON_TABLE
and JSON_QUERY
. For the full semantics of this clause, refer to JSON_path_expression in the documentation on JSON_QUERY
.JSON_table_on_error_clause
Use this clause to specify the value returned by this function when the following errors occur:
expr
is not well-formed JSON data using strict or lax JSON syntax- No match is found when the JSON data is evaluated using the row path expression
You can specify the following clauses:
NULL
ON
ERROR
- Returns null when an error occurs. This is the default.ERROR
ON
ERROR
- Returns the appropriate Oracle error when an error occurs.DEFAULT
literal
ON
ERROR
- Returnsliteral
when an error occurs. If the data type of the value returned by this function isVARCHAR2
, then you must specify a text literal. If the data type isNUMBER
, then you must specify a numeric literal.
Live home 3d pro edition 3.4.1. JSON_columns_clause
Use the
COLUMNS
clause to define the columns in the virtual relational table returned by the JSON_TABLE
function.JSON_exists_columnThis clause evaluates JSON data in the same manner as the
JSON_EXISTS
condition, that is, it determines if a specified JSON value exists. It returns either a VARCHAR2
column of values 'true
' or 'false
', or a NUMBER
column of values 1 or 0. A value of 'true
' or 1 indicates that the JSON value exists and a value of 'false
' or 0 indicates that the JSON value does not exist.You can use the
JSON_value_return_type
clause to control the data type of the returned column. If you omit this clause, then the data type is VARCHAR2(4000)
. Use column_name
to specify the name of the returned column. The rest of the clauses of JSON_exists_column
have the same semantics here as they have for the JSON_EXISTS
condition. For full information on these clauses, refer to 'JSON_EXISTS Condition'. Also see 'Using JSON_exists_column: Examples' for an example.JSON_query_columnThis clause evaluates JSON data in the same manner as the
JSON_QUERY
function, that is, it finds one or more specified JSON values, and returns a column of character strings that contain those JSON values.Use
column_name
to specify the name of the returned column. The rest of the clauses of JSON_query_column
have the same semantics here as they have for the JSON_QUERY
function. For full information on these clauses, refer to JSON_QUERY. Also see 'Using JSON_query_column: Example' for an example.JSON_value_columnThis clause evaluates JSON data in the same manner as the
JSON_VALUE
function, that is, it finds a specified scalar JSON value, and returns a column of those JSON values as SQL values.Use
column_name
to specify the name of the returned column. The rest of the clauses of JSON_value_column
have the same semantics here as they have for the JSON_VALUE
function. For full information on these clauses, refer to JSON_VALUE. Also see 'Using JSON_value_column: Example' for an example.JSON_nested_pathUse this clause to flatten JSON values in a nested JSON object or JSON array into individual columns in a single row along with JSON values from the parent object or array. You can use this clause recursively to project data from multiple layers of nested objects or arrays into a single row.
Specify the
JSON_path_expression
clause to match the nested object or array. This path expression is relative to the row path expression specified in the JSON_TABLE
function.Use the
COLUMNS
clause to define the columns of the nested object or array to be returned. This clause is recursive—you can specify the JSON_nested_path
clause within another JSON_nested_path
clause. Also see 'Using JSON_nested_path: Examples' for an example.ordinality_columnThis clause returns a column of generated row numbers of data type
NUMBER
. You can specify at most one ordinality_column
. Also see 'Using JSON_value_column: Example' for an example of using the ordinality_column
clause.Examples
Creating a Table That Contains a JSON Document: Example This example shows how to create and populate table
j_purchaseorder
, which is used in the rest of the JSON_TABLE
examples in this section.The following statement creates table
j_purchaseorder
. Column po_document
is for storing JSON data and, therefore, has an IS
JSON
check constraint to ensure that only well-formed JSON is stored in the column.The following statement inserts one row, or one JSON document, into table
j_purchaseorder
:Using JSON_query_column: Example The statement in this example queries JSON data for a specific JSON property using the
JSON_query_column
clause, and returns the property value in a column.The statement first applies a row path expression to column
po_document
, which results in a match to the ShippingInstructions
property. The COLUMNS
clause then uses the JSON_query_column
clause to return the Phone
property value in a VARCHAR2(100)
column.Using JSON_value_column: Example The statement in this example refines the statement in the previous example by querying JSON data for specific JSON values using the
JSON_value_column
clause, and returns the JSON values as SQL values in relational rows and columns.The statement first applies a row path expression to column
po_document
, which results in a match to the elements in the JSON array Phone
. These elements are JSON objects that contain two members named type
and number
. The statement uses the COLUMNS
clause to return the type
value for each object in a VARCHAR2(10)
column called phone_type
, and the number
value for each object in a VARCHAR2(20)
column called phone_num
. The statement also returns an ordinal column named row_number
.Using JSON_exists_column: Examples The statements in this example test whether a JSON value exists in JSON data using the
JSON_exists_column
clause. The first example returns the result of the test as a 'true
' or 'false
' value in a column. The second example uses the result of the test in the WHERE
clause.The following statement first applies a row path expression to column
po_document
, which results in a match to the entire context item, or JSON document. It then uses the COLUMNS
clause to return the requestor's name and a string value of 'true
' or 'false
' indicating whether the JSON data for that requestor contains a zip code. The COLUMNS
clause first uses the JSON_value_column
clause to return the Requestor
value in a VARCHAR2(32)
column called requestor
. It then uses the JSON_exists_column
clause to determine if the zipCode
object exists and returns the result in a VARCHAR2(5)
column called has_zip
.The following statement is similar to the previous statement, except that it uses the value of
has_zip
in the WHERE
clause to determine whether to return the Requestor
value:Using JSON_nested_path: Examples The following two simple statements demonstrate the functionality of the
JSON_nested_path
clause. They operate on a simple JSON array that contains three elements. The first two elements are numbers. The third element is a nested JSON array that contains two string value elements.The following statement does not use the
JSON_nested_path
clause. It returns the three elements in the array in a single row. The nested array is returned in its entirety.Json Editor 1.12 1 8
The following statement is different from the previous statement because it uses the
JSON_nested_path
clause to return the individual elements of the nested array in individual columns in a single row along with the parent array elements.The previous example shows how to use
JSON_nested_path
with a nested JSON array. The following example shows how to use the JSON_nested_path
clause with a nested JSON object by returning the individual elements of the nested object in individual columns in a single row along with the parent object elements.Json Editor Minecraft
The following statement uses the
JSON_nested_path
clause when querying the j_purchaseorder
table. It first applies a row path expression to column po_document
, which results in a match to the entire context item, or JSON document. It then uses the COLUMNS
clause to return the Requestor
value in a VARCHAR2(32)
column called requestor
. It then uses the JSON_nested_path
clause to return the property values of the individual objects in each member of the nested Phone
array. Note that a row is generated for each member of the nested array, and each row contains the corresponding Requestor
value.