Opticon ESL Server Manual page 39

If no Link-Table is supplied, then one will be automatically created (called "links") in the following
format:
CREATE TABLE links
(
[ID] VARCHAR(40),
[Variant] VARCHAR(1),
[MAC] VARCHAR(16) NOT NULL
)
If you wish to name the table or columns differently, this is allowed. You can do so by creating a
table with the same format, but different table and column names.
st
The 1 column (ID) should contain the unique product code.
nd column (Variant) should contain the ESL software variant ('H'=EE200/201, 'I'=EE201)
The 2
rd
The 3 column (MAC) should contain the MAC (or IEEE) addresses of the ESLs.
It is allowed to link the same product to multiple ESLs.
7.2.1.2 Link staging table
Staging tables are the interface tables between the remote database from the back office and the
local SQL databases used by the ESL server.
If no Link staging-Table is supplied, then one will be automatically created (called
"Links_Staging") in the following format:
CREATE TABLE links_staging
(
[ID] VARCHAR(40),
[Variant] VARCHAR(1),
[MAC] VARCHAR(16) NOT NULL
[DELETE] VARCHAR(1)
)
Changed links should be inserted in the link staging table and the ESL server will automatically
detect and process this data and insert the data into the Link table. If the processed data requires
an ESL to be updated, it will automatically generate a new image and sent it to the ESL.
The link staging table must have the same formatting as the link table, but should also contain a
'DELETE' column. The 'DELETE' column makes it possible to remove a link from the link table, by
placing an 'X' in this column*.
* Oracle requires the column 'DEL' instead of 'DELETE'
7.2.1.3 Product table
The product table should at least contain all the product information, which should be shown on
the automatically generated image of ESLs.
Example queries for each SQL database format and matching configurations can be found in:

Appendix B: My-SQL demo configuration
PRIMARY KEY
PRIMARY KEY,
39
Opticon ESL
ESL Server manual
v1.0.62.2