Recent content by Martin B

  1. M

    TOracleObject: Invalid handle error w/ NULL XMLType in query

    Only other thing to note is that this particular application uses pesistent fields in the datamodule (i.e. when TOracleQuery is executed in design mode and the fields are stored in the DM)
  2. M

    TOracleObject: Invalid handle error w/ NULL XMLType in query

    Hi Marco, Just observed some curious behavior in DOA v. 4.1.1. When we execute an query (or dataset) that has an XMLType column that is NULL we get an TOracleObject: Invalid handle when the corresponding Oracle session is freed. (Looks like DOA may be trying to free something that has a null...
  3. M

    Export to Excel Problem (Field Data begins with '=')

    Ditto. Using version 8.0.0.1480 A better implemtation of the workaround simply to add a ' prefix to the column data (i.e. prefixing every instance of = with ' is not necessary). SELECT ''''|| FROM [TABLE]; If Excel determines the column format as General it will balk at an entry beginning...
  4. M

    Oracle Client 10.2 and XMLTYPE

    Marco, I checked metalink and found that Oracle has classified bug 5846373 as unreproducable and "not a bug". (The original report said it was intermittent). If this is not an open issue with Oracle will you pursue the matter? -- it hapens consistently when creating an XMLType using DOA (v...
  5. M

    Oracle Client 10.2 and XMLTYPE

    I've encountered the same issue using the XMLType after migrating from 9.2.0.7 to the 10.2.0.3 client.
  6. M

    TOraclePackage and Timestamp

    On the database (Oracle) I have a TIMESTAMP, in Delphi I have a TDateTime.
  7. M

    TOraclePackage and Timestamp

    I have a PL/SQL package with some timestamp parameters (just plain timestamp, no timezone or local timezone) I delphi I hold the timestamp in a TDateTime attribute. e.g. Original date string: 24-JAN-2008 8:40:15.472 AM When using TOraclePackage to call the insert procedure I notice that the...
  8. M

    How to set a complex variable to NULL?

    Nevermind I think I have a solution... Creating an XMLType with a dummy string value, and then clearing the XMLType object makes it autonomically NULL. e.g. var MyXML: TXMLType begin MyXML := TXMLType.Create(Session,'') MyXML.Clear; // OBJECT Type is now autonomically NULL
  9. M

    How to set a complex variable to NULL?

    I am tyring to set a complex bind variable of type Object (TXMLType) to null. I have a string from which I build an XMLType. Sometimes that string is empty ''. The TXMLType.Create function always requires a valid XML string. Using a string of '' in the create function --...
  10. M

    Problems w/ Oracle Collection of Timestamp Values

    Oracle Client is 9.2.0.7 Database version is also 9.2.0.7
  11. M

    Problems w/ Oracle Collection of Timestamp Values

    When preforming a SELECT on an Oracle collection type (TABLE or VARRAY) of timestamp PL/SQL Developer does not repersent the collection corrcetly. The resulting collection is either returned as: or (after initial execution). Clicking on ... next to the displays no internal values (as it...
  12. M

    Unable to insert NULL value for TLobLocator

    I'm having trouble setting the value of a TLobLocator to null -- upon insert I always get an empty CLOB instead of a NULL vaule. I have tried using the SetEmpty as well as setting the AsString property of the TLobLocator to an empty string (MyLobLocator.AsString := ''). Also when useing...
  13. M

    Constraints on Nested table's Stroage Table not Captured

    Marco, After consulting Oracle's documentation some more there is some debate as to whether Oracle "officially" supports constraints on the storage table of a nested table. We're going to open a TAR with Oracle to get their response on the issue. Will keep you posted.
  14. M

    Object Type Evolution

    On generating DDL for an object type that has evolved over time. The resulting DDL is a cartesian procuct of the object's elements for each revision. e.g. /* DDL for object type with one evolutionary change see set-up below for original DDL */ CREATE OR REPLACE TYPE submitted_history_obj_t...
  15. M

    Constraints on Nested table's Stroage Table not Captured

    If a constraint is placed on a Nested Table's attribute the DDL extraction for the parent table does not capture that constraint, and as such is incopmplete. (Note the storage table does not appear under the USER_tables see SQL below. I do not know if this is Oracle's intended behavior.) /* ||...
Back
Top