Skip to content

Latest commit

 

History

History
74 lines (57 loc) · 2.39 KB

graph-id-from-edge-id-transact-sql.md

File metadata and controls

74 lines (57 loc) · 2.39 KB
title description author ms.author ms.date ms.service ms.subservice ms.topic f1_keywords helpviewer_keywords dev_langs monikerRange
GRAPH_ID_FROM_EDGE_ID (Transact-SQL)
GRAPH_ID_FROM_EDGE_ID (Transact-SQL)
arvindshmicrosoft
arvindsh
08/16/2022
sql
t-sql
reference
GRAPH_ID_FROM_EDGE_ID
GRAPH_ID_FROM_EDGE_ID function
Graph, system functions, graph ID, edge ID, edge
TSQL
= azuresqldb-current || >= sql-server-2017 || >= sql-server-linux-2017 || = azuresqldb-mi-current

GRAPH_ID_FROM_EDGE_ID (Transact-SQL)

[!INCLUDE SQL Server Azure SQL Database Azure SQL Managed Instance]

Returns the internal graph ID for a given edge ID.

Syntax

GRAPH_ID_FROM_EDGE_ID ( edge_id )

Arguments

edge_id

The character representation (JSON) of the $edge_id pseudo-column in an edge table.

Return value

Returns the internal graph ID, which is a bigint.

Remarks

  • Owing to the performance overhead of parsing and validating the supplied character representation (JSON) of edges, you should only use GRAPH_ID_FROM_EDGE_ID where needed. In most cases, MATCH should be sufficient for queries over graph tables.
  • For GRAPH_ID_FROM_EDGE_ID to return a value, the supplied character JSON must be valid and the named schema.table within the JSON, must be a valid edge table.
  • If a graph ID is returned by the function, it's only guaranteed that it will be a valid integer. No checks are made whether the graph ID is present in the edge table.
  • The data type and behavior of graph IDs are implementation specific details, and are subject to change. For example, you shouldn't assume that graph IDs in a given edge table are sequential.

Examples

The following example returns the internal graph ID for the edges in the friendOf edge table.

SELECT GRAPH_ID_FROM_EDGE_ID($edge_id)
FROM friendOf;

Here are the results:

...
25073
98943
69725
68781
30354
...

See also