Speed of XML vs SQLite

[xbury.cs at clearstream.com]

Thanks, confirms my worries...

Any tests between stack/card access and xml access for queries?

cheers
Xavier

On 23.05.2005 15:44:14 use-revolution-bounces wrote:
>Hi,
>
>For what it is worth, have a look at this:
>
>http://www.15seconds.com/issue/010410.htm
>(don't forget the first part)
>
>and at Mark Brownell's handlers and techniques as an option for rev's
>functions.
>
>Greetings,
>Wouter
>
>On 23 May 2005, at 14:57, Levi Kendall wrote:
>
>> Hi all,
>>
>>    I'm considering using XML for building a database but my concern is
>> that for data retrieval it might become very slow as more and more
>> data is added.  Would using functions such as revXMLMatchingNode be as
>> slow as doing a full text search of the xml or would it be at least
>> comparable to performing a lookup in an actual database?  Another
>> speed concern would be finding a node with multiple matching
>> attributes.  Is this a good idea or would I be better off using
>> something like SQLite?
>>
>> Thanks,
>> Levi
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>
>
>_______________________________________________
>use-revolution mailing list
>use-revolution at lists.runrev.com
>http://lists.runrev.com/mailman/listinfo/use-revolution


-----------------------------------------
Visit us at http://www.clearstream.com
IMPORTANT MESSAGE    Internet communications are not secure and therefore
Clearstream International does not accept legal responsibility for the
contents of this message.    The information contained in this e-mail is
confidential and may be legally privileged. It is intended solely for the
addressee. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it,
is prohibited and may be unlawful. Any views expressed in this e-mail are
those of the individual sender, except where the sender specifically states
them to be the views of Clearstream International or of any of its
affiliates or subsidiaries.    END OF DISCLAIMER