Man-wai Chang wrote on 2015-07-04: > I supposed it's not a RDBMS, but something like DBF. Am I correct? :) > > But is it as good and easy as DBF on a shared drive?
Man-wai, The way I related to what I read and heard about nosql is probably overly simplified. For a Customer you do one database call and it returns everything about the customer at once. When using a tool that can parse JSON or XML many layers deep it would be okay. To prevent a lag on the client side after retrieving the data, things are parsed from memory into the objects only when requested. So there is an apparent increase in speed. The data appears to be stored in what we might consider a memo field. Just one large JSON string with attached documents encoded inline. The main database time happens on the writes. It updates details about the customer in the customers document, it updates the orders in the orders document, and updates the unique customer document. Tracy Pearson PowerChurch Software _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
