RE: SECUREFILE keyword missing for BINARY XML

John Dorlon <[email protected]>
Newsgroups gmane.comp.db.oracle.toad.free
Message-ID <4120B436C765EC43A31CC3E2A13D36A6225C1B04@ALVMBXW02.prod.quest.corp>
Yes, I see that it is left off, but I think it is not needed.  When I create the table without the securefile kwd on binary xml, then get the script using dbms_metadata, I see it is still defined as securefile.  I'll fix it though,  it does seem misleading, at least.

From: [email protected] [mailto:[email protected]] On Behalf Of Paul Dziemiela
Sent: Monday, January 30, 2012 4:26 PM
To: [email protected]
Subject: [toad] SECUREFILE keyword missing for BINARY XML


Using Toad 11.0.0.116

CREATE TABLE foo
(
  trans_id         VARCHAR2(2000 BYTE),
  trans_user       VARCHAR2(2000 BYTE),
  trans_xml        SYS.XMLTYPE,
  trans_sdo        MDSYS.SDO_GEOMETRY
)
XMLTYPE trans_xml STORE AS SECUREFILE BINARY XML
VARRAY trans_sdo.SDO_ELEM_INFO STORE AS SECUREFILE LOB (
   ENABLE STORAGE IN ROW
)
VARRAY trans_sdo.SDO_ORDINATES STORE AS SECUREFILE LOB (
  ENABLE STORAGE IN ROW
);

The TOAD script playback misses the SECUREFILE keyword on the BINARY XML but it shows things fine on the VARRAY LOBs.

Note that I cannot actually view BINARY XML in a TOAD query grid without the application crashing (client 11.2.0.1 UTF8 instance).

Cheers,

Paul
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.