Hello Ivan,

Thanks very much for the suggestion.  I will look at the se:output
"indent=no" declaration, and study the import/export behavior further.

Malcolm

-----Original Message-----
From: Ivan Shcheklein [mailto:[email protected]] 
Sent: Thursday, July 07, 2011 2:41 PM
To: Malcolm Davis
Cc: [email protected]
Subject: Re: [Sedna-discussion] XML Storage

Malcolm,

Export/import (se_exp) preserves whitespaces. It uses boundary space
declaration (with preserve value) for that
http://www.w3.org/TR/xquery/#id-boundary-space-decls . So, if intentionally
created node with whitespaces inside you will have that node after
export/import.

I believe that se_BulkLoadFromStream is strip boundary whitespaces by
default. 

BTW, you can always check how Sedna actually stores data using se_term and 

declare option se:output "indent=no";

prolog declaration.

Ivan


        Good question: Are the documents auto flatten when loading using
Sedna
        se_BulkLoadFromStream?
        
        I'm using the Sedna Java libs, and se_BulkLoadFromStream is the root
call.
        In which case, this is a mute point and I can avoid the discussion.
        
        SednaAdmin.jar returns things formatted, but that might be a feature
        SednaAdmin and not how the docs are stored.
        
        Thanks,
        Malcolm
        
        
        
        When you export the files via se_exp all files are flatened. Sedna
should
        work internally only with nodes, not with xml documents as such -
flatening
        is useless, IMO.
        But I never tested it.
        
        Am 07.07.2011 19:29, schrieb Malcolm Davis:
        

               Does flattening the XML (removing white spaces, tabs, and
carriage
        returns) have any impact on storage and/or usage?
        
        
               From:
        
               <root>
        
                               <child>
        
                                               <fname>malcolm</fname>
        
                                               <lname>davis</lname>
        
                               </child>
        
               </root>
        
        
        
               To:
        
        
        
<root><child><fname>malcolm</fname><lname>davis</lname></child></root>
        
        
        
               It seems obvious that we would want to remove all unnecessary
        characters, but I want to verify as we put together our development
        document.
        
        
        
               Thanks,
        
               Malcolm
        
        
        
        
        
        
        
----------------------------------------------------------------------------
--
        All of the data generated in your IT infrastructure is seriously
valuable.
        Why? It contains a definitive record of application performance,
security
        threats, fraudulent activity, and more. Splunk takes this data and
makes
        sense of it. IT sense. And common sense.
        http://p.sf.net/sfu/splunk-d2d-c2
        _______________________________________________
        Sedna-discussion mailing list
        [email protected]
        https://lists.sourceforge.net/lists/listinfo/sedna-discussion
        




------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Sedna-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sedna-discussion

Reply via email to