... | ... | @@ -21,7 +21,7 @@ The table_definitions JSON has four attributes in the following format: |
|
|
~~~
|
|
|
|
|
|
* "pairing_description": <"string">
|
|
|
* Represents a brief description of what the table stores.
|
|
|
* Represents a brief description of what is stored by the tables.
|
|
|
<br/><br/>
|
|
|
|
|
|
* "data_source": <"string">
|
... | ... | @@ -29,14 +29,14 @@ The table_definitions JSON has four attributes in the following format: |
|
|
<br/><br/>
|
|
|
|
|
|
* "pk": <"list of strings, where each string represents a column of the table"> (Eg.: ["id", "year"])
|
|
|
* The table's primary key, it's needed at least one.
|
|
|
* The table's primary key. This field can have zero or more.
|
|
|
<br/><br/>
|
|
|
|
|
|
* "foreign_keys": <"list of strings, where each string represents a column of the table">
|
|
|
* Foreign keys of the table, can have zero or more.
|
|
|
* Foreign keys of the table. This field can have zero or more.
|
|
|
<br/><br/>
|
|
|
|
|
|
The hotmapper comes with an example of table definitions in the folder hotmapper/table_definitions, named
|
|
|
The HOTMapper comes with an example of table definitions in the folder hotmapper/table_definitions, named
|
|
|
example_table_definition.json and shown bellow.
|
|
|
|
|
|
~~~json
|
... | ... | |