So far the following restricted column names allowed from source database mssql affects postgres column names:
sample output from real transfer:
"error": "error running transfer 232ae647-d5ee-4174-9620-94d884c17711 :: error creating target table :: error running create table public.SampleTable :: error running ddl/dml on PostgreSQL Target :: create table if not exists public.SampleTable (TableID integer, ControlID integer, VisitTypeID integer, Order integer) :: ERROR: syntax error at or near \"Order\" (SQLSTATE 42601)",
Running the query manually by adding apostrophe around column name enables query to succeed.
Possibly solution, wrap all columns in apostrophe to allow sql parser to allow query execution.
So far the following restricted column names allowed from source database mssql affects postgres column names:
sample output from real transfer:
Running the query manually by adding apostrophe around column name enables query to succeed.
Possibly solution, wrap all columns in apostrophe to allow sql parser to allow query execution.