duursma

I'm working on a huge (I think) case for which it is not clear what the end goal is. For this I run into both structural issues and data issues....

And all I know is from reading your code :-(. In the Ora2Pg::format_data_row an effort is made to find the Oracle srid using parse_sdo_geometry. The SRID coming from that should...

The issue seems to me that 'current_setting(....)' is a value and can therefore not be assigned a value through INTO. Maybe a workaround would be to introduce a temporary variable...

I have updated a number of functions which I am currently testing. I'll add them once testing is finished. But I am mainly concentrating on Collection and Polygon. The above...

[geom.zip](https://github.com/darold/ora2pg/files/9126559/geom.zip)

I uploaded my version including some comments marked as #AD. Main 'feature' is that it loads a number of layers now without Postgres giving an error. It stops on a...

I would hope so. That is, the errors are gone and generated geometries are accepted by postgres.

It seems that the same is true for the --dbname and --port parameters. When using a service the other connection parameters are ignored.

The last message is: Jul 19, 2024 12:37:36 PM japicmp.output.incompatible.IncompatibleErrorOutput warn WARNING: Incompatibility detected: Requires semantic version level MAJOR: JApiMethod [oldMethod=net.sourceforge.pmd.lang.plsql.ast.PLSQLParserImpl.MergeUpdateClausePrefix(), newMethod=n.a., returnType=JApiReturnType [oldReturnTypeOptional=void, newReturnTypeOptional=value absent, changeStatus=REMOVED], getCompatibilityChanges()=[japicmp.model.JApiCompatibilityChange@5924303d]] This seems...

The no-longer-used function has been re-introduced. The updates and insert are now optional and infinitely repeatable. And all checks seem to pass.