[PostgreSQL/Oracle] Consistent treatment of spatial data
Database management in a single PHP file
Brought to you by:
jakubvrana
Menu
▾
▴
#615 [PostgreSQL/Oracle] Consistent treatment of spatial data
PostGIS geometries in PostgreSQL are shown as BYTEA, Oracle geometric tables seem empty because spatial columns prevents a query.
In the first case Adminer shows data that cannot be interpreted by the user, in the second case any geometric table seems empty. No records at all. Il would be possible to decode the geometry as well know text or just to tell what type of geometry is there.
Adminer does that for MySQL. If you know how to do it for other drivers, please send a pull request at https://github.com/vrana/adminer/.
For Oracle we tried to mimick the solution found in the driver for MySQL without success, adding the SDO_GEOMETRY data type to the array of types and converted/unconverted the geometry to/from text.
Adminer still lies, saying "No rows" for any table with a geometric column.
The issue is probably due to all geometric columns belonging to the MDSYS user in Oracle.