Gilles Darold
Gilles Darold
Thanks for the report #150 is solves but language is recognize as a plpgsql keyword which should not happen. I'll have a look
You are right, I will fix it again in the same commit.
Fixed by commit 5c7463d. Note that this patch break the form: ``` ... DO UPDATE SET (a, b, c) = (excluded.a, excluded.b, excluded.c); ``` I will try to fix this...
Commit 025004d fix the last issue.
@srinilakshmi, you write "not following" so I have understood that this issues was discarded. I have done some work recently to better support migration of input DDL script for SQL...
There is no solution, Ora2Pg use the parameters given at startup and duplicate the connection when forking process. This feature could be implemented the days I will encounter the problem...
Sequences need sometimes to be created before the tables because they are used. Actually the schema creation use `CREATE SCHEMA IF NOT EXISTS ...` which doesn't throw error. In other...
Right, but I normally the user importing sequences or other objects migrated by Ora2Pg might be the database owner or have enough privileges to create a schema. What is your...
Won't be fixed, I prefer the current behavior, you might find a solution to disable this line either by post export script or manually.
I have reviewed this problem and change my mind. Actually we are already adding the CREATE SCHEMA in table export only if CREATE_SCHEMA is enabled, so fo sequences it must...