Hi Todd,
I don't know how it would behave with a 100MB file but here is the
method I use to get the data from a particular node of the tree
without having to construct the full tree.
Best wishes,
Marielle
...
---
Ruslan-
Thursday, February 9, 2006, 1:28:53 PM, you wrote:
> Under proprietary may be you mean implementations of engines?
No, I'm referring to syntactical differences and proprietary
extensions. This is why XQuery was born, as an open-source standard to
try to rein this in.
> But this is not a
>> Also in ideal these tools must be able handle queries to XML document.
>> This can be Xpath, Xquery, or SQL/XML.
>
> ..and I'd advise staying away from XPath as well. It's gotten
> splintered into too many proprietary spinoffs.
>
> XQuery is much easier to read (IMO) and is pretty standardized
On Feb 9, 2006, at 1:01 PM, Mark Wieder wrote:
Todd-
Can you just work with the DTD? And then query the xml document for
data elements you're interested in?
I am not sure. But that might work
Todd
--
Todd Geist
__
g e i s t i n t e r a c t i v e
__
On 2/9/06 11:06 PM, "Mark Wieder" <[EMAIL PROTECTED]> wrote:
Hi Mark,
>> Also in ideal these tools must be able handle queries to XML document.
>> This can be Xpath, Xquery, or SQL/XML.
>
> ...and I'd advise staying away from XPath as well. It's gotten
> splintered into too many proprietary spin
> Also in ideal these tools must be able handle queries to XML document.
> This can be Xpath, Xquery, or SQL/XML.
...and I'd advise staying away from XPath as well. It's gotten
splintered into too many proprietary spinoffs.
XQuery is much easier to read (IMO) and is pretty standardized these
days
Todd-
Can you just work with the DTD? And then query the xml document for
data elements you're interested in?
--
-Mark Wieder
[EMAIL PROTECTED]
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubs
Hi Tuviah,
can write a SAX processor, in which case you won't have the whole
tree
in memory, but your sp
You can use revcreatexmltree, and just tell it to not build the dom
tree/or keep the document in memory, and handle the messages.
revCreateXMLTree(field "XML Data",true,false,true)
very
On 2/9/06 10:02 AM, "Ken Ray" <[EMAIL PROTECTED]> wrote:
>>> If I read it correctly, the answer is "no" - basically, with "true" as the
>>> last param, you're telling the DLL to send you a message when it's about to
>>> start parsing the tree, when it encounters each node (so you can extract
>>> a
On 2/9/06 9:15 AM, "Ken Ray" <[EMAIL PROTECTED]> wrote:
>>> You can use revcreatexmltree, and just tell it to not build the dom
>>> tree/or keep the document in memory, and handle the messages.
>>>
>>> revCreateXMLTree(field "XML Data",true,false,true)
>>
>> But won't that still choke on somethi
On 2/9/06 1:32 AM, "Todd Geist" <[EMAIL PROTECTED]> wrote:
>
> On Feb 8, 2006, at 11:15 PM, Ken Ray wrote:
>
>>
>> If I read it correctly, the answer is "no" - basically, with "true"
>> as the
>> last param, you're telling the DLL to send you a message when it's
>> about to
>> start parsing the
> Hello Everyone.
>
> I have some very large XML files ( 100mb or more) that I would to
> parse. And this thing has to be fast. I mean FAST. Since I have done
> almost no work with rev and XML, I am looking for advice on how to
> proceed
I've been asking the same questions of Emmanuel over at Sa
>
> On Feb 8, 2006, at 9:44 PM, [EMAIL PROTECTED] wrote:
>
>> You can use revcreatexmltree, and just tell it to not build the dom
>> tree/or keep the document in memory, and handle the messages.
>>
>> revCreateXMLTree(field "XML Data",true,false,true)
>
> But won't that still choke on something
On Feb 8, 2006, at 11:15 PM, Ken Ray wrote:
If I read it correctly, the answer is "no" - basically, with "true"
as the
last param, you're telling the DLL to send you a message when it's
about to
start parsing the tree, when it encounters each node (so you can
extract
attributes from the
On 2/8/06 11:26 PM, "Todd Geist" <[EMAIL PROTECTED]> wrote:
>
> On Feb 8, 2006, at 9:44 PM, [EMAIL PROTECTED] wrote:
>
>> You can use revcreatexmltree, and just tell it to not build the dom
>> tree/or keep the document in memory, and handle the messages.
>>
>> revCreateXMLTree(field "XML Data",
On Feb 8, 2006, at 9:44 PM, [EMAIL PROTECTED] wrote:
You can use revcreatexmltree, and just tell it to not build the dom
tree/or keep the document in memory, and handle the messages.
revCreateXMLTree(field "XML Data",true,false,true)
But won't that still choke on something as big as 100MB?
>can write a SAX processor, in which case you won't have the whole tree
>in memory, but your sp
You can use revcreatexmltree, and just tell it to not build the dom
tree/or keep the document in memory, and handle the messages.
revCreateXMLTree(field "XML Data",true,false,true)
Tuviah Snyder
www.md
On 2/8/06 8:59 PM, "Mark Wieder" <[EMAIL PROTECTED]> wrote:
Hi Mark,
Hi Todd,
> Todd-
>
> I'm with Ruslan on this one. DOM is the fastest way to access xml information,
> but the tree size will be huge (are you talking about a single 100MB file
> rather than multiple files adding up to 100MB?).
Todd-
I'm with Ruslan on this one. DOM is the fastest way to access xml
information, but the tree size will be huge (are you talking about a
single 100MB file rather than multiple files adding up to 100MB?). You
can write a SAX processor, in which case you won't have the whole tree
in memory, but
On 2/8/06 5:50 PM, "Todd Geist" <[EMAIL PROTECTED]> wrote:
Hi Todd,
> Hello Everyone.
>
> I have some very large XML files ( 100mb or more) that I would to
> parse. And this thing has to be fast. I mean FAST. Since I have done
> almost no work with rev and XML, I am looking for advice on how to
Hello Everyone.
I have some very large XML files ( 100mb or more) that I would to
parse. And this thing has to be fast. I mean FAST. Since I have done
almost no work with rev and XML, I am looking for advice on how to
proceed
The user experience needs to be some thing like this...
I sel
21 matches
Mail list logo
