Some of the objects in my script are not recognized by Migration Portal. What should I do?

Some of the objects in my script are not recognized by Migration Portal. What should I do?

Some of the objects in my script are not recognized by Migration Portal. What should I do? FYI, I have entered the DDL myself in the text area provided.

Accepted Solutions (0)

Answers (1)

Answers (1)

EDB Team Member

 

Possibly, there is space or any character after the semicolon that terminates SQL statement, remove it and the issue will be gone. Below are a few examples of both valid and invalid  DDL statements for migration portal assessment. 

 

Following will be assessed by EDB Migration Portal 

create table test (col1 int, col2 int);
create table test1 (col1 int -- integer column
                  , col2 int   -- another integer column
		    );

Following Statements will not be assessed by EDB Migration Portal 

create table test2 (col1 int, col2 int);  -- space after terminating semicolon.
create table test3 (col1 int, col2 int);a-- Alphabet after terminating semicolon.
create table test4 (col1 int, col2 int);$-- Special character after terminating semicolon.
create table test5 (col1 int, col2 int);1-- Numeric  after terminating semicolon.
create table test6 (col1 int, col2 int);;-- Two semicolons after closing parenthesis.
create table test7 (col1 int, col2 int); -- No extra space or semicolon, just comments.

 

 

 

Archived Discussions


Effective March 31st, we will no longer engage on PostgresRocks.


How to engage with us further?


  • Thought Leadership: EDB Blogs

  • Tips and Tricks: Postgres Tutorials

  • Customer Support: Create a Case Please note: Only customers with an active EDB support subscription and support portal authorization can create support ticket

  • Engage on Stackoverflow While engaging on Stackoverflow tag the question with EDB or EnterpriseDB.

© 2019 EnterpriseDB Corporation. All rights reserved.   |   Privacy Policy   |  Terms of Use   |   Trademarks