Changes between Version 2 and Version 3 of Ticket #1398


Ignore:
Timestamp:
09/22/10 11:05:23 (14 years ago)
Author:
brucedechant
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1398 – Description

    v2 v3  
    2525XERCES_CPP_NAMESPACE_QUALIFIER DOMDocument *getContentAsDOM(const DbXml::XmlValue &value);
    2626}}}
    27 It requires an !XmlValue and this is constructed by the constructor of the XmlValue class from the XmlDocument passed to it.
     27It requires an !XmlValue and this is constructed by the constructor of the !XmlValue class from the !XmlDocument passed to it.
    2828
    29 3.>Since XmlModify has been removed, we can use a simple Xquery Update to delete records. For example where our query was
    30 {{{ query = "/Role/Users/User[Name=<foobar>]"; }}} we change it to    {{{ query = "delete nodes /Role/Users/User[Name=<foobar>]"; }}} and just execute the query with XmlManager::query().
     293.>Since !XmlModify has been removed, we can use a simple Xquery Update to delete records. For example where our query was
    3130
    32 4.>The function for assigning flags to DbEnv has been changed from set_flags to log_set_config. The define LOG_INMEMORY is no longer defined. It has been replaced with LOG_IN_MEMORY, which is functionally equivalent.
     31{{{
     32query = "/Role/Users/User[Name=<foobar>]";
     33}}}
     34we change it to
     35{{{
     36query = "delete nodes /Role/Users/User[Name=<foobar>]";
     37}}}
     38and just execute the query with XmlManager::query().
    3339
    34 5.>Included db_cxx.h . Also removed the 'catch' for DbException. This isnt completely necessary but seeing that DbXml wants to encapsulate DbException inside XmlException and the functionality was similar, I removed it.
     404.>The function for assigning flags to !DbEnv has been changed from set_flags to log_set_config. The define LOG_INMEMORY is no longer defined. It has been replaced with LOG_IN_MEMORY, which is functionally equivalent.
     41
     425.>Included db_cxx.h . Also removed the 'catch' for !DbException. This isnt completely necessary but seeing that !DbXml wants to encapsulate !DbException inside !XmlException and the functionality was similar, I removed it.
    3543{{{
    3644catch (XmlException& e)                                                   \
    … …  
    7684    }                     
    7785}}}
    78 Since XmlException would be triggered on a DbException and would give the same DbErrno and what() string, it seemed redundant to include this. Note the initial motivation was this to go with the philosophy of dbxml of hiding DB as much as possible. Unfortunately due to MapGuides use of DB objects in multiple places, that won't be possible.
     86Since !XmlException would be triggered on a !DbException and would give the same !DbErrno and what() string, it seemed redundant to include this. Note the initial motivation was this to go with the philosophy of dbxml of hiding DB as much as possible. Unfortunately due to MapGuide's use of DB objects in multiple places, that won't be possible.
    7987
    80 6.>As there is no other option, but to go with LiveValues and afaik there appears to be no difference, I have just removed the lines.
     886.>As there is no other option, but to go with !LiveValues and afaik there appears to be no difference, I have just removed the lines.
    8189
    8290