You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 8, 2022. It is now read-only.
Dears!
It wolud be great if you may change name of each key column and iindexes etc.
to contain tablename to be unique in scope of the database device.
Pls, use id_tablename index and key columnn etc.
In case of more tables (from different IPs) it is conflict with the same id name of index.
Values are stored into incorrect tables then.
Publish call error: pq: relation "key_index" already exists
So use :
id_key_[tablename],
index_[tablename] etc...
because tablename is unique in scope of database.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Dears!
It wolud be great if you may change name of each key column and iindexes etc.
to contain tablename to be unique in scope of the database device.
Pls, use id_tablename index and key columnn etc.
In case of more tables (from different IPs) it is conflict with the same id name of index.
Values are stored into incorrect tables then.
Thanks very much.
Best Regards,
Richard
tablename:
logs_192x162x010x050
logs_192x162x010x060
Publish call error: pq: relation "key_index" already exists
So use :
id_key_[tablename],
index_[tablename] etc...
because tablename is unique in scope of database.
The text was updated successfully, but these errors were encountered: