Just what gets through both selects. The query is performed on the SQL host (IBMi) and what comes back is just the result set. The result set is meted out in chunks, so if you only read the first record and closed the connection, the umpteenth wouldn't cross the wire unless you had the block size set really high.
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Tuesday, April 19, 2011 4:08 PM
To: 'Java Programming on and around the IBM i'
Subject: How does access through JDBC work, anyway?
Suppose we do a SELECT on a VIEW, and the VIEW itself contains a SELECT, perhaps one that calls a scalar UDF (can we do this?).
The SELECT within the VIEW would be to censor the data, so that the user doesn't see records he/she isn't entitled to; the SELECT *on* the VIEW would be to find the records he/she is interested in.
Just how much data gets sent to the JDBC client? The whole megillah?
Just what the VIEW returns after its internal SELECT? Or just the records that get through both SELECTs?
This is the Java Programming on and around the IBM i (JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l
As an Amazon Associate we earn from qualifying purchases.