RE: Directions for Java/400

>I've been hearing some of the same 'proprietary software' responses when
>suggesting these tools.  And I guess it is a good point, since we have not
>yet committed to the AS/400 as our server (my bias notwithstanding).
--------
I hope for your company's sake they listen to your bias <smile>.



Joe, have you done any testing to see if your stuff is as fast, faster,
whatever, compared to SQL?
--------
Not a lot, but I don't need a lot.  Other than the magic of stored procedures
(which I'm not too familiar with, but the last time I looked was pretty
non-portable), there's just no way SQL can match up to native AS/400 database
I/O for true transactional stuff.  It's great for queries, hence it's name, but
it's lousy for transaction processing (which is probably why it's called "SQL"
rather than "STPL").

Anyway, a simple inconclusive test:

Inserting 10000 records into a file consisting of two L-dates and a character
field.

SQL:      17 seconds
Native:   2 seconds

There's no contest.

Joe


+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---