This will create an Embed token and override the properties specified for specific dataset(s) serviced by the MariaDB connection** When doing connection overrides, it's important that the schema of the tables in the override conform to the same schema as the original datasets to avoid query failures due to schema mismatches The fields available for overriding a MariaDB connection are as follows
Connection ID: The ID of the Connection to be overridden. Retrieve the ID to specify as detailed here
host: The new database host to connect to. The database must be of the same type as the originally configured database
port: The new port to connect to
user: The new user to use when connecting
password: The new password to use when connecting
database: The new schema to retrieve data from. Note that to MariaDB the concepts database and schema are identical. So when overriding a database / schema for MariaDB, make sure to pass the same value for both schema and database
schema: The new schema to retrieve data from. Note that to MariaDB the concepts database and schema are identical. So when overriding a database / schema for MariaDB, make sure to pass the same value for both schema and database
table: The new table to retrieve data from
datasets: List of dataset-level overrides. Useful if you want to override only a single dataset in your dashboard or if you have a separate table per client. The SQL query of the dataset can also be overridden if it's a SQL dataset within Luzmo
schema: the new schema to connect to
table: The new MariaDB table to query.
sql: The new SQL query to run (only for SQL datasets ). Alternatively, you could also use parameterized SQL Datasets .
npm install @luzmo/nodejs-sdk