Hi Stefanos,
I remember trying to do it but fail to. I didn't try too hard though so
maybe it's possible, but IIRC there were some triggers involved
that complicated things.
I'm afraid about others problems that could come then.
Regards,
Julien
> Hi Julien,
> do you think updating the crs
Hi Julien,
do you think updating the crs definition in MDSYS.CS_SRS with a proper one
could be a workaround for such cases or would it introduce other problems?
Stefanos
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
___
Hi,
I'm pretty sure this is the same issue than this one:
https://github.com/qgis/QGIS/issues/37898
Long story short, Oracle definition for projection differs from PROJ
database ones. So this exception needs to be taken care of. It's done in
PROJ > 7.1 but QGIS 3.16 and 3.18 relies on PROJ
Hello,
We are having a problem displaying our data from our Oracle database.
Our data stored in our Oracle database has the EPSG code as a projection: 2154.
We have configured Qgis with the following parameters:
- Project CRS: EPSG 2154: RGF 93 / Lambert-93
- Layer CRS: use the project CRS
