SQLFlow Data Reference¶
Target Fields Data¶
-
id
id of the target column * name
name of the target column. the name would be the caller if the Relationship type is
call
* columncolumn name * function
fucntion name if the relationship is from a function * target_id
target id if the target is not on column level * target_name
target name if the target is not on column level * parent_id
parent id of the target's parent node * parent_name
parent name of the target's parent node * parent_alias
parent alias of the target's parent node * coordinate * source
will be filtered out on UI if the source is from system * type
type of the storage process if the Relationship type is
call
. could be:procedure
,function
,trigger
,macro
Source Fields Data¶
-
id
source column Id * name
caller name if the Relationship type is
call
* column * source column name * source_idsource id when the source is not on column level * source_name
source name when the source is not on column level * column_type
column type * parent_id
source parent node id * parent_name
source parent node name * parent_alias
source parent node alias * coordinate * clauseType
source clause type * source
will be filtered out on UI if the source is from system * type
type of the storage process if the Relationship type is
call
. could be:procedure
,function
,trigger
,macro
subnode in the SourceColumn
-
transforms
Belongs to the Transform Structure
Transform Fields Data¶
Describe how the Relationship is generated
-
type
type, could be:
simple
,function
,expression
,constant
,case
orsubquery
* coordinate * codecode expression
Table Structure¶
-
id
table id * server
db server to which the table belongs * database
database to which the table belongs * schema * table schema * name
table name,
database.schema.table
for example. if there's no database the name would beschema.table
. If there's no schema the name will bedatabase.table
* aliasalias name * uri
mapped url when table type is
file, path, stage
orstream
* typetable type * subType
subtype of the type * processIds
linked process Ids * fileType
mapped file type if the table type is stage * fileFormat
mapped file format if table type is ```
_
file, path, stage_ or _
stream`_ * locationlocation url if the table type is
stage
ordatasource
* isTargetif display in UI * coordinate
element coordinate * parent
storage process of the table * more
if collaspe in the UI
Subnode in Table structure:
-
column
Belongs to the Column Structure
Column Structure¶
- id
- column id
- name
- column name
- coordinate
- column coordinate
-
source
column source. will not be dispalyed If source is
system
* qualifiedTable * Field which is used to distinguish the column when there are columns under the same name such as: table1.a, table2.a
OraclePackage Structure¶
-
id
package id * server
db server to which the package belongs * database
database to which the package belongs * schema
schema to which the package belongs * name
package name:
database.schema.package
The name would be :schema.package
If there's no database . The name would bedatabase.package
if there 's no schema. * typepackage type * coordinate
package coordinate
Subnode in OraclePackage structure:
-
procedure
Belongs to the Procedure Structure
Procedure Structure¶
-
id
procedure id * server
db server to which the procedure belongs * database
database to which the procedure belongs * schema
schema to which the procedure belongs * name
procedure name:
database.schema.procedure
The name would be :schema.procedure
If there's no database . The name would bedatabase.procedure
if there 's no schemaif the procedure belongs to package, full name will also contain package segment * type
procedure type, could be
procedure
,function
,trigger
* coordinateprocedure coordinate
Subnode in procedure structure:
-
argument
Belongs to the Argument Structure
Argument Structure¶
Argument is to describe the parameters during the storage process
-
id
argument id * name
argument name * coordinate
argument coordinate * datatype
argument data type * inout
in or out type
Process Structure¶
Process will be generated when data flow moves from one table to another
- id
- process id
-
server
db server to which the process belongs * database
database to which the process belongs * schema
schema to which the process belongs * name
process name, different process can have the same name * procedureName
procedure to which the process belongs * procedureId
procedure id to which the process belongs * queryHashId
statement hashcode to which the process belongs * type
process type * coordinate
process coordinate