Using non-symbol identifiers for getTicks¶
Enabling non-symbol identifiers¶
Create a .domain.cfg.paramscfg file, which will contain the row(s) being updated to allow for further data types to be used in the getTicks API call. As a default symbol atoms or vectors are used (-11 11h).
Example of .domain.cfg.paramscfg¶
.domain.cfg.paramscfg: flip `funcName`paramName`paramType`default`isRequired`paramTypes ! flip (enlist ( `getTicks ; `idList ; `S ; "" ; 1b ; -11 11h));
| funcName | paramName | paramType | default | isRequired | paramTypes |
|---|---|---|---|---|---|
| getTicks | idList | S | "" | 1 | -11 11 |
Note
Either change or add data types to the last column in the above example.
Real-world example, a client uses GUIDs as their identifier for their financial data. By adding -2 2 to your collection of allowed data types, a GUID can now be used in the API calls to query the database.
guidID: "G"$"bc50fb62-6479-4f65-98fe-b4a7cca9e8ef";
.gwClient.query.sync[`getTicks; `dataSource`dataType`startDate`endDate`idList ! (`source; `tableName; .z.d; .z.d; guidID) ]
Note
This works for all data types