Problem trying to execute Reverse DDL from PostgreSQL DDL.sql file

I am still working on an evaluation copy of the enterprise edition of VP. I am trying to REVERSE DDL. I created the DDL file from within the JetBrains Datagrip product. When I execute the REVERSE DDL from VP I point to the DDL created from Datagrip which is a SQL file and then I get this error in VP:

[12:58:20] [Error] Fail to reverse PostgreSQL database DDL: C:\Users\msavoy\Documents\qa_salesdb_DDL_script.sql. Parse error at line 420, column 21. Encountered: if

Here is line 420 in the DDL script:
create unique index if not exists pg_default_acl_role_nsp_obj_index

Can someone please help ASAP? Thanks.

Hi Melinda,

We’ll provide a patch to support this syntax soon.

Hi, I would like to let you know the unable to reverse PostgreSQL DDL problem has been fixed. Please update the software to latest patch build (20200230as or later) to get the problem fixed. Details about update to latest patch can be found at

  • Please make sure you have pressed the “Update to latest patch” button on the left hand side of the dialog right after launching the update program

Feel free to contact me if you require any further information.

Best regards,
Rain Wong

Hi Rain,

I executed the latest patch build as you instructed and now I’m getting this error from the log:

[06:53:57] [Error] Fail to reverse PostgreSQL database DDL: H:\SprintTasks\5_MarketingProject\SM-46 - PostgreSQL Database Design for Sales Portal\SQLScripts\qa_salesdb_DDL_Script.sql. Parse error at line 8144, column 86. Encountered: nulls

The REVERSE DDL appears to have gotten past the error I reported above but now I have this error.

I sent you the .SQL file so that you can test on your end in the email to the support-team@visual-paradigm.com. Again, this was created in the JetBrains Datagrip product. Please let me know if you can fix this so that I can continue with the evaluation. Appreciate your help.

Thanks for the sample file and I would like to let you know the problem has been fixed again. Please update the software to latest patch build (20200230ay or later) to get the problem fixed. Feel free to contact me if you require any further information.