We are doing some testing with PostgreSQL and Timescale and I am finding that when we connect to the database that has Timescale configured Ignition is browsing dozens of tables in specific schemas that Timescale made.
My question is, how do I tell Ignition in the database connection string to only browse the public schema that contains the actual Ignition tables? I have tried setting the search_path to public for my ignition user configured in PostgreSQL and I have also tired setting ?currentSchema=public in the Ignition db connect string.
Should I be using the extra connection properties field instead? Thanks!
What is the actual connection url?
I have a postgres connection set up like this:
connect url: jdbc:postgresql://localhost:5432/ignition
extra connection properties: currentSchema=public
1 Like
The connection URL is: postgresql://xxx.xxx.xxx.xxx:5432/test
extra connection properties: currentSchema=public
EDIT:
As you can see even with this setup there are a lot of extra tables that are coming from other schemas:
did you ever find any solution? I want to do something similar, I want to create a new schema in timescale, and a single database connection to only that, and hide all of the public tables. the currentSchema prop seems to prevent the system from interacting with those other tables , but they still show up in the list and its a bit messy.
one thing that can be done is in the database translator, you can set it to exclude certain table names like hyper and those wont show up but theres still a lot of other noise.
No I did not. In fact, we found that the Timescale was about the same performance as MSSQL so it was not worth continuing to fight it.