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
This is for a clarification regarding the table name in transaction log.
In Postgres, while creating table to preserve case sensitivity to the table name will get it enclosed within double quotes.
Eg: public."SRCTABLE"
So while receiving an transaction log for this particular table getting the table name enclosed within double quotes. i.e: "public.\"SRCTABLE\""
Here, i need to know is this a correct behaviour since i assumed i will be receiving the table name similar to how it gets stored in the Postgres DB.
The text was updated successfully, but these errors were encountered:
That's correct. It uses the same rule as PostgreSQL. You can say that it is not the case for some use cases (and I agree) so we could add an option to not include quotes.
@eulerto I feel it will be really helpful if we have an additional filter option to not include quotes for the table names. If we have that, we can have a same behaviour for all table names irrespective of any case.
This is for a clarification regarding the table name in transaction log.
In Postgres, while creating table to preserve case sensitivity to the table name will get it enclosed within double quotes.
Eg: public."SRCTABLE"
So while receiving an transaction log for this particular table getting the table name enclosed within double quotes. i.e:
"public.\"SRCTABLE\""
Here, i need to know is this a correct behaviour since i assumed i will be receiving the table name similar to how it gets stored in the Postgres DB.
The text was updated successfully, but these errors were encountered: