4 Replies Latest reply on Jan 28, 2012 12:44 AM by Gary Graham-Oracle

    SQLD 3.1EA -  Fails to render resultset output containing SDO_GEOMETRY

      Was really hoping (after being reassured it would be fixed in the next release) that this would be sorted, but isn't.
      Attempting to pull back records with SDO_GEOMETRY, even with a modest number of rows, will cause SQLD to sit at 100% CPU resources indefinitely.

      A suitable work around may be to write an alternative to oracle.sql.SRUCT.toString() that is considerably shorter and quicker to execute, maybe just providing some summary information (SRID, GTYPE, # of rings, # of points) rather than the gory detail.