On Wed, Aug 19, 2009 at 23:22, Nathan Andelin<nandelin@xxxxxxxxx> wrote:
use full commitment control and journalling for everything

It would really surprise me if SAP's benchmarks included journaling.

They do. tlogs aren't optional in other RDBMS. Except in MySQL with
MyISAM tables, which is a special case.

But my order entry applications follow a traditional header-line model, where the order is entered, then a series of line items are entered. ÂEach entry adds or changes a record on the server, immediately.

And there is never ever any need in your application to change more
than one row at a time?

Under my header-line model, there's no need for commitment control. ÂBut RPG-based commitment control doesn't add much overhead, if or when needed.

Well, i don't see ACID in a business critical application as "optional".

Well, I subscribe to the old adage - make everything as simple as possible. ÂIn this case, the IBM i HTTP server forwards browser requests to an RPG-based server which natively interfaces with the database, then returns an HTML/JavaScript response.

Yep, but "Notepad is faster than Word" is hardly news. Even if the
machine running notepad is slower.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].