jdbc-prof report

Recording: C:\p_drafts\jdbc-lens\sample-app\sample-recording.jdbclog
Events
14208
DB time
214.21 ms
Wall time
3.50 s
Templates
51
Call-sites
144

Severity

25 Idle locks — worst gap 133.88 ms 19 N+1 — biggest 8.35 ms 1 Wide UPDATEs — 9 columns 25 Write amplification 1 Commit-per-record — biggest run 17.86 ms 3 Walk-and-fetch 14 Redundant queries 295 Entity audit 145 Read-then-write

Source scan: 8 of 9 tables exercised at runtime — 1 unexercised; recording may be missing code paths

Top call-sites by DB time

  1. fi.vesas.jdbclens.sample.dao.OrderDao.insert:91 — 16.15 ms across 200 events
  2. fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 — 13.68 ms across 100 events
  3. fi.vesas.jdbclens.capture.CapturingPreparedStatement.executeBatch:301 — 11.93 ms across 1 events
Flamegraph

Widths are total DB time. Hover any frame for its full class + line.

all app code — 180.76 ms
main — 28.33 ms
run — 13.68 ms
countByCustomer — 13.68 ms
run — 8.35 ms
sumAmountByCustomer — 8.35 ms
run — 2.59 ms
insert — 2.59 ms
run — 2.53 ms
latestOrderAtByCustomer — 2.53 ms
run — 1.18 ms
findByCustomer — 1.18 ms
main — 24.01 ms
createSchema — 7.25 ms
execute — 7.25 ms
emitExecuteUnknown — 7.25 ms
emitExecuteUnknown — 7.25 ms
createSchema — 5.90 ms
execute — 5.90 ms
emitExecuteUnknown — 5.90 ms
emitExecuteUnknown — 5.90 ms
createSchema — 4.91 ms
execute — 4.91 ms
emitExecuteUnknown — 4.91 ms
emitExecuteUnknown — 4.91 ms
createSchema — 1.99 ms
execute — 1.99 ms
emitExecuteUnknown — 1.99 ms
emitExecuteUnknown — 1.99 ms
createSchema — 772.50 us
execute — 772.50 us
emitExecuteUnknown — 772.50 us
emitExecuteUnknown — 772.50 us
createSchema — 688.50 us
execute — 688.50 us
emitExecuteUnknown — 688.50 us
emitExecuteUnknown — 688.50 us
createSchema — 670.20 us
execute — 670.20 us
emitExecuteUnknown — 670.20 us
emitExecuteUnknown — 670.20 us
createSchema — 665.90 us
execute — 665.90 us
emitExecuteUnknown — 665.90 us
emitExecuteUnknown — 665.90 us
createSchema — 601.70 us
execute — 601.70 us
emitExecuteUnknown — 601.70 us
emitExecuteUnknown — 601.70 us
createSchema — 560.10 us
execute — 560.10 us
emitExecuteUnknown — 560.10 us
emitExecuteUnknown — 560.10 us
main — 16.15 ms
insert — 16.15 ms
main — 12.83 ms
run — 8.20 ms
processDetailRecords — 7.15 ms
readNextDetail — 7.15 ms
processDetailRecords — 1.05 ms
readDetailFields — 1.05 ms
run — 2.83 ms
readNextMaster — 2.83 ms
run — 1.29 ms
writeMasterBreak — 1.29 ms
run — 506.50 us
readMasterFields — 506.50 us
main — 12.25 ms
placeOrders — 7.54 ms
insert — 7.54 ms
placeOrders — 4.71 ms
getByKey — 4.71 ms
main — 11.93 ms
seed — 11.93 ms
executeBatch — 11.93 ms
main — 10.06 ms
listDashboard — 9.55 ms
findById — 9.55 ms
listDashboard — 506.30 us
findRecent — 506.30 us
main — 9.16 ms
run — 5.64 ms
readNextKey — 5.64 ms
run — 1.81 ms
rewriteMasterRecord — 1.81 ms
run — 1.13 ms
invalidKeyCheck — 1.13 ms
run — 577.50 us
readMasterRecord — 577.50 us
main — 8.06 ms
refundLatest — 2.98 ms
findLatestByCustomer — 2.98 ms
refundLatest — 2.72 ms
log — 2.72 ms
refundLatest — 2.36 ms
markRefunded — 2.36 ms
main — 7.35 ms
applyFlatDiscount — 4.33 ms
updateAmount — 4.33 ms
applyFlatDiscount — 2.94 ms
findLatestByCustomer — 2.94 ms
applyFlatDiscount — 87.10 us
findRecent — 87.10 us
main — 5.96 ms
completeCheckout — 2.85 ms
recordCheckout — 1.26 ms
log — 1.26 ms
recordCheckout — 932.60 us
log — 932.60 us
recordCheckout — 662.10 us
findEmailById — 662.10 us
completeCheckout — 816.50 us
getByKey — 816.50 us
completeCheckout — 793.70 us
insert — 793.70 us
completeCheckout — 780.30 us
findById — 780.30 us
completeCheckout — 720.90 us
getByKey — 720.90 us
main — 4.84 ms
buildTopReport — 4.56 ms
topCustomersBySpend — 4.56 ms
buildTopReport — 272.50 us
findFullById — 272.50 us
main — 3.86 ms
drain — 1.65 ms
markSent — 1.65 ms
drain — 1.20 ms
log — 1.20 ms
drain — 951.20 us
markFailed — 951.20 us
drain — 56.00 us
listPending — 56.00 us
main — 3.25 ms
migrateTimezone — 2.43 ms
updateAll — 2.43 ms
migrateTimezone — 820.70 us
findFullById — 820.70 us
main — 3.22 ms
searchByKeyword — 3.22 ms
findByNameLike — 3.22 ms
main — 3.16 ms
enrich — 990.40 us
resolveCurrencyLabel — 990.40 us
enrich — 841.50 us
resolveShippingLabel — 841.50 us
enrich — 811.60 us
resolveStatusLabel — 811.60 us
enrich — 517.30 us
readOrder — 517.30 us
main — 2.72 ms
run — 2.72 ms
processCustomers — 2.72 ms
processOne — 2.72 ms
buildFor — 1.34 ms
loadSpending — 1.34 ms
countByCustomer — 1.34 ms
buildFor — 982.50 us
recordStatement — 982.50 us
log — 982.50 us
buildFor — 403.90 us
loadProfile — 403.90 us
findFullById — 403.90 us
main — 2.64 ms
renderFeaturedItem — 2.64 ms
countByCustomer — 2.64 ms
main — 2.45 ms
purgeProcessedOutboxEvents — 2.45 ms
main — 2.36 ms
finalizeShipment — 1.21 ms
markShipped — 1.21 ms
finalizeShipment — 1.15 ms
updateStatus — 1.15 ms
main — 1.82 ms
updatePhone — 1.28 ms
updateAll — 1.28 ms
updatePhone — 542.50 us
findFullById — 542.50 us
main — 1.03 ms
enqueue — 1.03 ms
main — 827.60 us
refresh — 827.60 us
touchLastSeen — 827.60 us
main — 656.10 us
exportAll — 656.10 us
fetchPage — 656.10 us
main — 520.70 us
seedProducts — 520.70 us
executeBatch — 520.70 us
main — 462.40 us
batchFetchByIds — 462.40 us
findByIds — 462.40 us
main — 271.50 us
searchByKeyword — 271.50 us
findByNameLike — 271.50 us
main — 258.40 us
seedCodes — 150.30 us
seedCodes — 54.60 us
seedCodes — 53.50 us
main — 258.00 us
searchByKeyword — 258.00 us
findByNameLike — 258.00 us
main — 53.10 us
trimAuditLog — 53.10 us
Operations

One bar per invocation of Profiler.currentOperation(name). Position is wall-clock start; width is that invocation's duration. Hover a bar for details.

0 ms 3.50 s monthly-reconciliation monthly-reconciliation span=44.29 ms events=2300 DB time=29.63 ms schema schema span=30.36 ms events=11 DB time=24.02 ms seed-orders seed-orders span=42.78 ms events=600 DB time=17.53 ms seed-customers seed-customers span=32.86 ms events=4 DB time=14.22 ms match-master-detail match-master-detail span=29.06 ms events=1980 DB time=13.85 ms place-orders place-orders span=26.00 ms events=1600 DB time=13.15 ms list-dashboard list-dashboard span=27.46 ms events=1205 DB time=12.62 ms product-search product-search span=14.90 ms events=56 DB time=12.21 ms post-master-update post-master-update span=17.86 ms events=1140 DB time=10.66 ms refund-latest refund-latest span=135.50 ms events=12 DB time=632.90 us refund-latest span=121.21 ms events=12 DB time=355.80 us refund-latest span=125.08 ms events=12 DB time=366.90 us refund-latest span=123.28 ms events=12 DB time=504.60 us refund-latest span=125.38 ms events=12 DB time=423.50 us refund-latest span=126.04 ms events=12 DB time=545.60 us refund-latest span=125.38 ms events=12 DB time=525.70 us refund-latest span=124.19 ms events=12 DB time=307.40 us refund-latest span=124.07 ms events=12 DB time=373.80 us refund-latest span=124.36 ms events=12 DB time=383.60 us refund-latest span=124.22 ms events=12 DB time=381.40 us refund-latest span=124.70 ms events=12 DB time=334.90 us refund-latest span=125.24 ms events=12 DB time=321.10 us refund-latest span=126.11 ms events=12 DB time=381.90 us refund-latest span=126.19 ms events=12 DB time=304.30 us refund-latest span=122.08 ms events=12 DB time=262.30 us refund-latest span=124.91 ms events=12 DB time=332.10 us refund-latest span=124.52 ms events=12 DB time=328.00 us refund-latest span=128.15 ms events=12 DB time=285.20 us refund-latest span=124.03 ms events=12 DB time=472.70 us refund-latest span=124.70 ms events=12 DB time=496.60 us refund-latest span=125.37 ms events=12 DB time=417.90 us refund-latest span=124.02 ms events=12 DB time=328.90 us refund-latest span=123.59 ms events=12 DB time=379.60 us refund-latest span=124.62 ms events=12 DB time=360.50 us apply-flat-discount apply-flat-discount span=13.29 ms events=905 DB time=7.83 ms order-report order-report span=9.91 ms events=65 DB time=6.94 ms complete-checkout complete-checkout span=7.77 ms events=29 DB time=871.90 us complete-checkout span=566.90 us events=29 DB time=365.80 us complete-checkout span=391.10 us events=29 DB time=193.20 us complete-checkout span=415.00 us events=29 DB time=220.30 us complete-checkout span=391.80 us events=29 DB time=192.70 us complete-checkout span=462.50 us events=29 DB time=246.50 us complete-checkout span=376.60 us events=29 DB time=203.30 us complete-checkout span=373.20 us events=29 DB time=198.30 us complete-checkout span=369.00 us events=29 DB time=197.90 us complete-checkout span=369.70 us events=29 DB time=189.30 us complete-checkout span=418.50 us events=29 DB time=235.50 us complete-checkout span=413.40 us events=29 DB time=206.30 us complete-checkout span=606.50 us events=29 DB time=373.60 us complete-checkout span=585.80 us events=29 DB time=364.10 us complete-checkout span=380.80 us events=29 DB time=197.60 us complete-checkout span=474.20 us events=29 DB time=282.40 us complete-checkout span=515.10 us events=29 DB time=330.80 us complete-checkout span=380.60 us events=29 DB time=180.50 us complete-checkout span=405.10 us events=29 DB time=227.70 us complete-checkout span=473.80 us events=29 DB time=244.80 us complete-checkout span=383.40 us events=29 DB time=201.00 us complete-checkout span=348.50 us events=29 DB time=172.90 us complete-checkout span=340.90 us events=29 DB time=179.10 us complete-checkout span=391.10 us events=29 DB time=174.60 us complete-checkout span=373.90 us events=29 DB time=202.10 us outbox-dispatch outbox-dispatch span=10.88 ms events=334 DB time=6.13 ms render-hot-item render-hot-item span=5.30 ms events=50 DB time=4.88 ms enrich-with-codes enrich-with-codes span=10.15 ms events=1200 DB time=3.63 ms migrate-timezone migrate-timezone span=6.39 ms events=480 DB time=3.40 ms purge purge span=3.33 ms events=8 DB time=3.13 ms daily-report daily-report span=5.92 ms events=390 DB time=3.12 ms finalize-shipment finalize-shipment span=1.82 ms events=6 DB time=370.40 us finalize-shipment span=166.90 us events=6 DB time=92.40 us finalize-shipment span=147.70 us events=6 DB time=88.00 us finalize-shipment span=158.70 us events=6 DB time=96.90 us finalize-shipment span=146.40 us events=6 DB time=84.80 us finalize-shipment span=165.50 us events=6 DB time=100.00 us finalize-shipment span=142.10 us events=6 DB time=83.50 us finalize-shipment span=164.60 us events=6 DB time=105.70 us finalize-shipment span=152.30 us events=6 DB time=85.20 us finalize-shipment span=153.10 us events=6 DB time=94.40 us finalize-shipment span=172.30 us events=6 DB time=108.00 us finalize-shipment span=143.40 us events=6 DB time=85.40 us finalize-shipment span=186.90 us events=6 DB time=115.60 us finalize-shipment span=147.30 us events=6 DB time=84.10 us finalize-shipment span=147.40 us events=6 DB time=89.70 us finalize-shipment span=147.30 us events=6 DB time=89.90 us finalize-shipment span=141.70 us events=6 DB time=83.80 us finalize-shipment span=163.70 us events=6 DB time=100.20 us finalize-shipment span=182.10 us events=6 DB time=108.80 us finalize-shipment span=184.30 us events=6 DB time=119.40 us finalize-shipment span=156.80 us events=6 DB time=87.90 us finalize-shipment span=173.50 us events=6 DB time=103.50 us finalize-shipment span=156.30 us events=6 DB time=85.80 us finalize-shipment span=157.40 us events=6 DB time=85.30 us finalize-shipment span=150.00 us events=6 DB time=84.60 us heartbeat heartbeat span=3.00 ms events=90 DB time=2.28 ms update-profile update-profile span=1.17 ms events=8 DB time=327.50 us update-profile span=153.40 us events=8 DB time=74.30 us update-profile span=114.50 us events=8 DB time=65.40 us update-profile span=137.70 us events=8 DB time=74.60 us update-profile span=114.50 us events=8 DB time=63.50 us update-profile span=130.00 us events=8 DB time=67.00 us update-profile span=123.20 us events=8 DB time=73.80 us update-profile span=110.70 us events=8 DB time=62.00 us update-profile span=116.20 us events=8 DB time=62.30 us update-profile span=165.40 us events=8 DB time=98.30 us update-profile span=118.00 us events=8 DB time=66.40 us update-profile span=127.70 us events=8 DB time=73.70 us update-profile span=114.10 us events=8 DB time=63.50 us update-profile span=112.40 us events=8 DB time=61.10 us update-profile span=115.60 us events=8 DB time=66.90 us update-profile span=134.90 us events=8 DB time=85.10 us update-profile span=120.20 us events=8 DB time=71.50 us update-profile span=132.30 us events=8 DB time=81.60 us update-profile span=135.30 us events=8 DB time=71.80 us update-profile span=152.40 us events=8 DB time=97.80 us update-profile span=143.80 us events=8 DB time=85.30 us update-profile span=133.00 us events=8 DB time=75.40 us update-profile span=146.70 us events=8 DB time=95.90 us update-profile span=130.50 us events=8 DB time=80.10 us update-profile span=112.20 us events=8 DB time=62.80 us paginated-export paginated-export span=4.11 ms events=255 DB time=1.23 ms outbox-seed outbox-seed span=3.56 ms events=150 DB time=1.17 ms seed-products seed-products span=1.42 ms events=4 DB time=774.80 us schema-extend schema-extend span=870.00 us events=5 DB time=738.30 us

Wall is the clock time the op took end-to-end. DB is how much of that was spent inside JDBC calls. The split bar is DB (blue) vs. non-DB (gray) — a mostly-gray bar means the app, network, or external I/O is where the time went, not the database.

OperationWallDBNon-DBDB vs. non-DBEventsTemplates
monthly-reconciliation44.29 ms29.63 ms14.65 ms
23005
schema30.36 ms24.02 ms6.34 ms
1110
seed-orders42.78 ms17.53 ms25.25 ms
6001
seed-customers32.86 ms14.22 ms18.64 ms
41
match-master-detail29.06 ms13.85 ms15.21 ms
19805
place-orders26.00 ms13.15 ms12.84 ms
16002
list-dashboard27.46 ms12.62 ms14.84 ms
12052
product-search14.90 ms12.21 ms2.70 ms
562
post-master-update17.86 ms10.66 ms7.20 ms
11404
refund-latest3.13 s9.81 ms3.12 s
3003
apply-flat-discount13.29 ms7.83 ms5.45 ms
9053
order-report9.91 ms6.94 ms2.98 ms
652
complete-checkout18.98 ms6.45 ms12.52 ms
7255
outbox-dispatch10.88 ms6.13 ms4.75 ms
3344
render-hot-item5.30 ms4.88 ms422.20 us
501
enrich-with-codes10.15 ms3.63 ms6.52 ms
12002
migrate-timezone6.39 ms3.40 ms3.00 ms
4802
purge3.33 ms3.13 ms200.00 us
82
daily-report5.92 ms3.12 ms2.79 ms
3903
finalize-shipment5.67 ms2.63 ms3.04 ms
1502
heartbeat3.00 ms2.28 ms718.50 us
901
update-profile4.77 ms2.11 ms2.67 ms
2002
paginated-export4.11 ms1.23 ms2.88 ms
2551
outbox-seed3.56 ms1.17 ms2.39 ms
1501
seed-products1.42 ms774.80 us648.80 us
41
schema-extend870.00 us738.30 us131.70 us
51
(no operation)64.60 us64.60 us0 ns
10
Transactions holding locks during non-DB work

Each TX below committed or rolled back at least one write, but between two of its statements the app spent real time outside the database — usually an HTTP call, a file read, or heavy CPU work. Row/page locks taken by the earlier writes were held the whole time. The call-site listed below each bar is where execution was when the gap started: that's almost always where the non-DB work is happening.

133.88 ms idle 99% of a 135.50 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
127.71 ms idle 100% of a 128.15 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
125.77 ms idle 100% of a 126.19 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
125.56 ms idle 100% of a 126.11 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
125.26 ms idle 99% of a 126.04 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
124.80 ms idle 100% of a 125.38 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
124.77 ms idle 100% of a 125.37 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
124.75 ms idle 100% of a 125.24 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
124.60 ms idle 99% of a 125.38 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
124.51 ms idle 100% of a 125.08 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
124.38 ms idle 100% of a 124.91 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
124.20 ms idle 100% of a 124.70 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
124.09 ms idle 100% of a 124.62 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
124.01 ms idle 100% of a 124.52 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
123.96 ms idle 99% of a 124.70 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
123.70 ms idle 99% of a 124.36 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
123.70 ms idle 100% of a 124.19 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
123.63 ms idle 100% of a 124.22 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
123.51 ms idle 100% of a 124.02 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
123.50 ms idle 100% of a 124.07 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
123.29 ms idle 99% of a 124.03 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
123.02 ms idle 100% of a 123.59 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
122.46 ms idle 99% of a 123.28 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
121.64 ms idle 100% of a 122.08 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
120.68 ms idle 100% of a 121.21 ms transaction
read write idle longest gap commit
operation
refund-latest
app was here
(unattributed)
next statement
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
locks held
UPDATE orders SET refunded = TRUE WHERE id = ?
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
suggestion
Move the non-DB work outside the transaction, or split into two transactions around the gap. If the inner work must run atomically, commit first and retry compensating work on failure.
Commit-per-record runs

Each card below is a run of many short explicit transactions fired back-to-back from the same outer method. Each TX did only a handful of statements and committed — the signature of a loop that commits every iteration (a per-object ORM save inside a for, or any per-record commit() in batch code). Cards are ranked by total wall time the pattern consumed.

60× 17.86 ms total wall · 288.92 us avg per TX
inside operation
post-master-update
loop body here
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
outer loop (probable fix)
fi.vesas.jdbclens.capture.CapturingConnection.prepareStatement:99
per-TX shape
1 writes · 3 reads
statements in one iteration
SELECT MIN(ID) FROM CUSTOMERS WHERE ID > ?
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ?
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ?
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ?
total DB time in run
10.66 ms
suggestion
Widen the transaction boundary so a batch of records shares one commit(). Each commit costs a WAL flush and a client round-trip; amortising that across 50–500 records typically reclaims most of the run's wall time. If atomicity is per-record by design, consider whether the commit is what's needed or whether a savepoint + single outer commit would suffice.
N+1 findings

A template fired many times from one call-site — usually a loop that runs one query per row instead of one batched query. Parameters typically differ per call (one ID per row). Cards are ranked by total DB time; count is across the whole recording. See Redundant queries below for the identical-parameters variant.

100× 8.35 ms total DB time
template
SELECT SUM(amount) FROM orders WHERE customer_id = ?
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65
outer loop (probable fix)
fi.vesas.jdbclens.sample.batch.ReconciliationJob.run:52
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
158× 7.15 ms total DB time
template
SELECT MIN(ID) FROM ORDERS WHERE CUSTOMER_ID = ? AND ID > ?
query fires here
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readNextDetail:111
outer loop (probable fix)
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.processDetailRecords:64
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
100× 4.33 ms total DB time
template
UPDATE orders SET amount = ? WHERE id = ?
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.updateAmount:118
outer loop (probable fix)
fi.vesas.jdbclens.sample.service.BulkOpsService.applyFlatDiscount:51
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
100× 2.59 ms total DB time
template
INSERT INTO customer_balances (customer_id, orders_count, lifetime_spend, last_order_at, updated_at) VALUES (?, ?, ?, ?, ?)
query fires here
fi.vesas.jdbclens.sample.dao.BalanceDao.insert:51
outer loop (probable fix)
fi.vesas.jdbclens.sample.batch.ReconciliationJob.run:59
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
100× 2.53 ms total DB time
template
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80
outer loop (probable fix)
fi.vesas.jdbclens.sample.batch.ReconciliationJob.run:53
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
25× 2.36 ms total DB time
template
UPDATE orders SET refunded = TRUE WHERE id = ?
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.markRefunded:47
outer loop (probable fix)
fi.vesas.jdbclens.sample.service.RefundService.refundLatest:35
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
60× 1.81 ms total DB time
template
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ?
query fires here
fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
outer loop (probable fix)
fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.run:63
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
43× 1.65 ms total DB time
template
UPDATE outbox_events SET status = 'SENT', processed_at = ? WHERE id = ?
query fires here
fi.vesas.jdbclens.sample.dao.OutboxDao.markSent:57
outer loop (probable fix)
fi.vesas.jdbclens.sample.batch.OutboxDispatcher.drain:48
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
50× 1.29 ms total DB time
template
INSERT INTO AUDIT (KIND, PAYLOAD, TS) VALUES (?, ?, ?)
query fires here
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.writeMasterBreak:145
outer loop (probable fix)
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.run:53
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
25× 1.21 ms total DB time
template
UPDATE orders SET shipped_at = ? WHERE id = ?
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109
outer loop (probable fix)
fi.vesas.jdbclens.sample.service.OrderService.finalizeShipment:82
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
100× 1.18 ms total DB time
template
SELECT customer_id, orders_count, lifetime_spend, last_order_at FROM customer_balances WHERE customer_id = ?
query fires here
fi.vesas.jdbclens.sample.dao.BalanceDao.findByCustomer:31
outer loop (probable fix)
fi.vesas.jdbclens.sample.batch.ReconciliationJob.run:57
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
25× 1.15 ms total DB time
template
UPDATE orders SET status = ? WHERE id = ?
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100
outer loop (probable fix)
fi.vesas.jdbclens.sample.service.OrderService.finalizeShipment:81
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
60× 1.13 ms total DB time
template
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ?
query fires here
fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120
outer loop (probable fix)
fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.run:64
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
50× 1.03 ms total DB time
template
INSERT INTO outbox_events (kind, payload, status, created_at) VALUES (?, ?, 'PENDING', ?)
query fires here
fi.vesas.jdbclens.sample.dao.OutboxDao.enqueue:30
outer loop (probable fix)
fi.vesas.jdbclens.sample.Main.main:215
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
30× 827.60 us total DB time
template
UPDATE sessions SET last_seen = CURRENT_TIMESTAMP WHERE id = ?
query fires here
fi.vesas.jdbclens.sample.dao.SessionDao.touchLastSeen:13
outer loop (probable fix)
fi.vesas.jdbclens.sample.service.SessionService.refresh:18
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
25× 662.10 us total DB time
template
SELECT email FROM customers WHERE id = ?
query fires here
fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24
outer loop (probable fix)
fi.vesas.jdbclens.sample.service.NotificationService.recordCheckout:38
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
11× 656.10 us total DB time
template
SELECT id, name, email FROM customers LIMIT ? OFFSET ?
query fires here
fi.vesas.jdbclens.sample.service.PaginatedExportService.fetchPage:42
outer loop (probable fix)
fi.vesas.jdbclens.sample.service.PaginatedExportService.exportAll:24
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
60× 577.50 us total DB time
template
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ?
query fires here
fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
outer loop (probable fix)
fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.run:54
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
50× 506.50 us total DB time
template
SELECT ID, NAME FROM CUSTOMERS WHERE ID = ?
query fires here
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readMasterFields:98
outer loop (probable fix)
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.run:48
suggestion
Replace the inner query with a batched/join query that returns all rows in one round-trip, or fetch the full collection once and pass it through.
Walk-and-fetch loops

A pair of templates whose shape betrays row-at-a-time access through hand-written SQL: one query walks a key column with MIN / MAX and a strict inequality, the other fetches row fields by that same key. Both queries live under the same outer method. The fix is not the usual N+1 batch-or-join — it's to replace the pair with one scrolling ResultSet, or one set-oriented GROUP BY. Nested pairs (a walk-and-fetch loop inside another walk-and-fetch loop) are flagged — those are almost always replaceable with a single JOIN … GROUP BY.

158 walks × 108 fetches 8.20 ms total DB time
walked table
orders.id
walk
SELECT MIN(ID) FROM ORDERS WHERE CUSTOMER_ID = ? AND ID > ? — fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readNextDetail:111
fetch
SELECT ID, AMOUNT, STATUS FROM ORDERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readDetailFields:125
outer method
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.processDetailRecords:64
nested in
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.run:44 — another emulated cursor is already walking above this one
suggestion
Two walk-and-fetch loops nested inside each other. Almost always a master/detail traversal that a single SELECT … FROM orders JOIN … GROUP BY would replace — the row-at-a-time shape hides set semantics that the analyzer can recover from the call pattern.
60 walks × 60 fetches 6.77 ms total DB time
walked table
customers.id
walk
SELECT MIN(ID) FROM CUSTOMERS WHERE ID > ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readNextKey:79
fetch
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120
outer method
fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.run:50
suggestion
Replace the walk + fetch pair with one scrolling ResultSet (SELECT … FROM customers ORDER BY id) and iterate it via ResultSet.next(). Each iteration then costs one row, not two round-trips.
50 walks × 50 fetches 3.34 ms total DB time
walked table
customers.id
walk
SELECT MIN(ID) FROM CUSTOMERS WHERE ID > ? — fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readNextMaster:84
fetch
SELECT ID, NAME FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readMasterFields:98
outer method
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.run:44
suggestion
Replace the walk + fetch pair with one scrolling ResultSet (SELECT … FROM customers ORDER BY id) and iterate it via ResultSet.next(). Each iteration then costs one row, not two round-trips.
Write patterns

Wide UPDATEs

9 columns SET 85 executions · 3.70 ms
template
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ?
call-site
fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Only SET the columns that actually changed. Every wide UPDATE fires triggers, CDC, and replication for no-op changes and muddies audit diffs.

UPDATE-then-UPDATE on the same row

Two or more UPDATEs landed on the same row inside one operation — each a separate round-trip, trigger fire, CDC event, and replication message. The overlap label tells you the flavour: mergeable means disjoint SET columns that collapse cleanly into one UPDATE; overlapping means some columns get written twice (the last write wins — often a stale copy from a different service); redundant means the exact same SET clause fired more than once.

2× UPDATE 155.60 us total DB time ·
entity
orders.id = 1
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 96.20 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 59.40 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 117.00 us total DB time ·
entity
orders.id = 48
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 62.80 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 54.20 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 113.00 us total DB time ·
entity
orders.id = 157
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 66.70 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 46.30 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 106.20 us total DB time ·
entity
orders.id = 35
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 46.00 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 60.20 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 105.50 us total DB time ·
entity
orders.id = 131
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 55.70 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 49.80 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 103.60 us total DB time ·
entity
orders.id = 92
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 41.80 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 61.80 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 101.00 us total DB time ·
entity
orders.id = 74
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 42.20 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 58.80 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 97.90 us total DB time ·
entity
orders.id = 22
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 38.80 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 59.10 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 97.40 us total DB time ·
entity
orders.id = 66
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 38.70 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 58.70 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 94.60 us total DB time ·
entity
orders.id = 40
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 41.90 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 52.70 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 92.10 us total DB time ·
entity
orders.id = 118
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 50.00 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 42.10 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 89.40 us total DB time ·
entity
orders.id = 14
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 46.10 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 43.30 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 87.60 us total DB time ·
entity
orders.id = 196
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 40.40 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 47.20 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 87.40 us total DB time ·
entity
orders.id = 183
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 40.00 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 47.40 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 85.80 us total DB time ·
entity
orders.id = 27
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 38.80 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 47.00 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 85.70 us total DB time ·
entity
orders.id = 61
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 40.60 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 45.10 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 83.40 us total DB time ·
entity
orders.id = 87
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 39.20 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 44.20 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 83.10 us total DB time ·
entity
orders.id = 144
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 39.60 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 43.50 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 83.00 us total DB time ·
entity
orders.id = 105
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 41.20 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 41.80 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 82.80 us total DB time ·
entity
orders.id = 100
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 42.10 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 40.70 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 82.50 us total DB time ·
entity
orders.id = 53
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 40.10 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 42.40 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 82.00 us total DB time ·
entity
orders.id = 113
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 38.30 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 43.70 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 81.80 us total DB time ·
entity
orders.id = 170
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 39.50 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 42.30 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 81.60 us total DB time ·
entity
orders.id = 9
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 39.90 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 41.70 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
2× UPDATE 81.20 us total DB time ·
entity
orders.id = 79
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 40.90 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 40.30 us
suggestion
Collapse into one UPDATE that sets all of the columns at once. One round-trip, one trigger fire, one CDC event.
In-operation redundancy

Repeated queries with identical parameters

The same template fired more than once with identical parameters inside one logical operation — usually a lookup that should be cached or fetched once and passed through the call chain. Different from N+1 above: N+1 repeats a template with different parameters (a loop over rows); a redundant finding repeats it with identical parameters (no caching). Cards are ranked by total DB time.

200× 4.71 ms total DB time
template
SELECT v FROM settings WHERE k = ?
inside operation
place-orders
query fires here
fi.vesas.jdbclens.sample.dao.SettingsDao.getByKey:14
parameters
[1] k=max_order_value
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.
10× 2.64 ms total DB time
template
SELECT COUNT(*) FROM orders WHERE customer_id = ?
inside operation
render-hot-item
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55
parameters
[1] customer_id=1
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.
60× 990.40 us total DB time
template
SELECT V FROM SETTINGS WHERE K = ?
inside operation
enrich-with-codes
query fires here
fi.vesas.jdbclens.sample.cobol.CodeLookupService.resolveCurrencyLabel:79
parameters
[1] K=currency_label_EUR
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.
60× 841.50 us total DB time
template
SELECT V FROM SETTINGS WHERE K = ?
inside operation
enrich-with-codes
query fires here
fi.vesas.jdbclens.sample.cobol.CodeLookupService.resolveShippingLabel:99
parameters
[1] K=shipping_label_STD
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.
25× 816.50 us total DB time
template
SELECT v FROM settings WHERE k = ?
inside operation
complete-checkout
query fires here
fi.vesas.jdbclens.sample.dao.SettingsDao.getByKey:14
parameters
[1] k=max_order_value
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.
60× 811.60 us total DB time
template
SELECT V FROM SETTINGS WHERE K = ?
inside operation
enrich-with-codes
query fires here
fi.vesas.jdbclens.sample.cobol.CodeLookupService.resolveStatusLabel:89
parameters
[1] K=status_label_OPEN
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.
25× 720.90 us total DB time
template
SELECT v FROM settings WHERE k = ?
inside operation
complete-checkout
query fires here
fi.vesas.jdbclens.sample.dao.SettingsDao.getByKey:14
parameters
[1] k=default_currency
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.
39.70 us total DB time
template
SELECT id, amount FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1
inside operation
apply-flat-discount
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.findLatestByCustomer:37
parameters
[1] customer_id=148
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.
34.40 us total DB time
template
SELECT id, amount FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1
inside operation
apply-flat-discount
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.findLatestByCustomer:37
parameters
[1] customer_id=141
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.
34.20 us total DB time
template
SELECT id, amount FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1
inside operation
apply-flat-discount
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.findLatestByCustomer:37
parameters
[1] customer_id=127
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.
33.80 us total DB time
template
SELECT id, amount FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1
inside operation
apply-flat-discount
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.findLatestByCustomer:37
parameters
[1] customer_id=134
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.
33.70 us total DB time
template
SELECT id, amount FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1
inside operation
apply-flat-discount
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.findLatestByCustomer:37
parameters
[1] customer_id=169
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.
33.50 us total DB time
template
SELECT id, amount FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1
inside operation
apply-flat-discount
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.findLatestByCustomer:37
parameters
[1] customer_id=162
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.
31.90 us total DB time
template
SELECT id, amount FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1
inside operation
apply-flat-discount
query fires here
fi.vesas.jdbclens.sample.dao.OrderDao.findLatestByCustomer:37
parameters
[1] customer_id=155
suggestion
Cache the result for the duration of the operation, or fetch it once at the top and pass the value through the call chain. If the lookup is cheap and the call path is short, confirm with the team that caching is worth the invalidation cost before changing anything.

Multiple templates touching the same entity

3 templates 6.16 ms total DB time · 3 events
entity
orders.customer_id = 17
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 5.96 ms
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 165.60 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 35.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 1.12 ms total DB time · 3 events
entity
orders.customer_id = 1
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 823.20 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 246.60 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 51.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 349.30 us total DB time · 3 events
entity
orders.customer_id = 20
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 172.00 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 90.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 87.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 317.00 us total DB time · 3 events
entity
orders.customer_id = 14
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 183.50 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 100.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 33.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 285.00 us total DB time · 3 events
entity
orders.customer_id = 2
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 137.90 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 104.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 43.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 260.70 us total DB time · 3 events
entity
orders.customer_id = 5
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 119.70 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 94.90 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 46.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 260.10 us total DB time · 3 events
entity
orders.customer_id = 9
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 107.00 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 93.70 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 59.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 244.60 us total DB time · 3 events
entity
orders.customer_id = 13
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 109.20 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 97.70 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 37.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 243.40 us total DB time · 3 events
entity
orders.customer_id = 15
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 121.20 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 105.60 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 16.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 242.90 us total DB time · 3 events
entity
orders.customer_id = 22
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 122.10 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 95.20 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 25.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 238.40 us total DB time · 3 events
entity
orders.customer_id = 7
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 105.20 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 95.10 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 38.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 237.80 us total DB time · 3 events
entity
orders.customer_id = 6
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 109.60 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 91.60 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 36.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 234.40 us total DB time · 3 events
entity
orders.customer_id = 18
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 107.50 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 96.10 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 30.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 233.70 us total DB time · 3 events
entity
orders.customer_id = 21
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 107.70 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 96.60 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 29.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 230.80 us total DB time · 3 events
entity
orders.customer_id = 4
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 99.80 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 96.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 35.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 229.40 us total DB time · 3 events
entity
orders.customer_id = 10
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 101.30 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 98.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 30.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 228.40 us total DB time · 3 events
entity
orders.customer_id = 24
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 101.00 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 91.40 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 36.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 228.20 us total DB time · 3 events
entity
orders.customer_id = 12
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 99.90 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 96.30 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 32.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 227.10 us total DB time · 3 events
entity
orders.customer_id = 3
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 102.00 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 95.80 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 29.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 222.90 us total DB time · 3 events
entity
orders.customer_id = 23
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 104.50 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 89.20 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 29.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 221.60 us total DB time · 3 events
entity
orders.customer_id = 16
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 99.30 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 94.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 28.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 220.70 us total DB time · 3 events
entity
orders.customer_id = 11
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 96.30 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 92.50 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 31.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 220.20 us total DB time · 3 events
entity
orders.customer_id = 40
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 113.10 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 79.70 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 27.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 212.70 us total DB time · 3 events
entity
orders.customer_id = 25
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 107.20 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 82.10 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 23.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 207.80 us total DB time · 3 events
entity
orders.customer_id = 26
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 88.60 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 82.40 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 36.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 207.30 us total DB time · 3 events
entity
orders.customer_id = 33
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 96.10 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 84.30 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 26.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 206.80 us total DB time · 3 events
entity
orders.customer_id = 27
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 94.50 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 84.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 28.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 203.40 us total DB time · 3 events
entity
orders.customer_id = 8
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 96.10 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 92.50 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 14.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 201.60 us total DB time · 3 events
entity
orders.customer_id = 37
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 104.10 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 75.90 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 21.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 201.00 us total DB time · 3 events
entity
orders.customer_id = 42
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 97.10 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 74.30 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 29.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 200.40 us total DB time · 3 events
entity
orders.customer_id = 32
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 87.70 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 86.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 26.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 197.90 us total DB time · 3 events
entity
orders.customer_id = 19
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 84.30 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 84.10 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 29.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 197.90 us total DB time · 3 events
entity
orders.customer_id = 44
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 101.30 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 74.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 22.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 197.00 us total DB time · 3 events
entity
customers.id = 1
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 100.10 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 64.00 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 32.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 195.60 us total DB time · 3 events
entity
orders.customer_id = 41
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 89.60 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 83.70 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 22.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 195.50 us total DB time · 3 events
entity
orders.customer_id = 28
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 83.70 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 82.40 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 29.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 195.50 us total DB time · 3 events
entity
orders.customer_id = 48
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 99.90 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 72.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 23.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 194.10 us total DB time · 3 events
entity
orders.customer_id = 39
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 93.50 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 75.70 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 24.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 194.10 us total DB time · 3 events
entity
orders.customer_id = 51
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 98.50 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 74.60 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 21.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 190.90 us total DB time · 3 events
entity
orders.customer_id = 52
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 84.20 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 82.10 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 24.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 190.00 us total DB time · 3 events
entity
orders.customer_id = 54
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 108.70 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 60.20 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 21.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 189.80 us total DB time · 3 events
entity
orders.customer_id = 34
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 84.30 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 81.50 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 24.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 188.70 us total DB time · 3 events
entity
orders.customer_id = 43
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 90.70 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 85.20 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 12.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 188.00 us total DB time · 3 events
entity
orders.customer_id = 31
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 84.10 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 79.70 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 24.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 185.70 us total DB time · 3 events
entity
orders.customer_id = 38
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 88.70 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 73.80 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 23.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 183.70 us total DB time · 3 events
entity
orders.customer_id = 30
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 82.40 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 78.40 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 22.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 183.70 us total DB time · 3 events
entity
orders.customer_id = 46
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 87.10 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 74.90 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 21.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 182.00 us total DB time · 3 events
entity
orders.customer_id = 36
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 86.60 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 82.80 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 12.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 181.00 us total DB time · 3 events
entity
orders.customer_id = 49
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 79.10 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 73.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 28.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 180.20 us total DB time · 3 events
entity
orders.customer_id = 29
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 86.40 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 81.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 12.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 179.90 us total DB time · 3 events
entity
orders.customer_id = 45
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 81.40 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 75.20 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 23.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 178.70 us total DB time · 3 events
entity
orders.customer_id = 35
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 78.50 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 78.10 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 22.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 174.20 us total DB time · 3 events
entity
orders.customer_id = 96
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 93.00 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 61.40 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 19.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 172.70 us total DB time · 3 events
entity
orders.customer_id = 50
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 80.40 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 79.60 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 12.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 170.60 us total DB time · 3 events
entity
orders.customer_id = 53
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 75.90 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 73.40 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 21.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 168.80 us total DB time · 3 events
entity
orders.customer_id = 47
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 74.40 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 73.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 21.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 161.90 us total DB time · 3 events
entity
orders.customer_id = 74
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 71.30 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 66.40 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 24.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 160.00 us total DB time · 3 events
entity
orders.customer_id = 64
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 84.20 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 60.90 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 14.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 158.50 us total DB time · 3 events
entity
orders.customer_id = 65
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 74.80 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 56.60 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 27.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 156.90 us total DB time · 3 events
entity
orders.customer_id = 68
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 74.80 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 56.60 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 25.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 155.60 us total DB time · 2 events
entity
orders.id = 1
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 96.20 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 59.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 155.40 us total DB time · 3 events
entity
orders.customer_id = 98
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 84.00 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 51.10 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 20.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 152.90 us total DB time · 3 events
entity
orders.customer_id = 100
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 68.60 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 65.10 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 19.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 152.40 us total DB time · 3 events
entity
orders.customer_id = 66
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 64.40 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 61.10 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 26.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 151.20 us total DB time · 3 events
entity
orders.customer_id = 94
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 70.60 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 61.20 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 19.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 150.10 us total DB time · 3 events
entity
orders.customer_id = 71
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 76.60 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 52.10 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 21.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 148.70 us total DB time · 3 events
entity
orders.customer_id = 82
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 78.60 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 50.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 20.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 146.70 us total DB time · 3 events
entity
orders.customer_id = 62
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 62.90 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 56.90 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 26.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 145.70 us total DB time · 3 events
entity
orders.customer_id = 59
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 68.00 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 55.90 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 21.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 142.30 us total DB time · 3 events
entity
orders.customer_id = 73
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 64.80 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 51.40 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 26.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 142.30 us total DB time · 2 events
entity
customers.id = 92
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 115.20 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 27.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 141.40 us total DB time · 3 events
entity
orders.customer_id = 61
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 58.90 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 56.10 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 26.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 136.80 us total DB time · 3 events
entity
orders.customer_id = 60
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 55.00 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 54.60 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 27.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 136.20 us total DB time · 3 events
entity
orders.customer_id = 85
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 70.00 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 53.30 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 12.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 136.00 us total DB time · 3 events
entity
orders.customer_id = 84
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 63.30 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 51.80 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 20.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 134.60 us total DB time · 3 events
entity
orders.customer_id = 58
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 58.90 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 52.40 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 23.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 133.70 us total DB time · 3 events
entity
orders.customer_id = 80
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 57.50 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 56.30 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 19.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 132.90 us total DB time · 3 events
entity
orders.customer_id = 63
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 53.90 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 52.80 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 26.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 130.70 us total DB time · 3 events
entity
orders.customer_id = 67
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 56.90 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 51.20 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 22.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 129.90 us total DB time · 3 events
entity
orders.customer_id = 69
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 52.90 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 50.70 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 26.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 129.70 us total DB time · 3 events
entity
orders.customer_id = 72
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 51.70 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 50.60 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 27.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 129.60 us total DB time · 3 events
entity
orders.customer_id = 55
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 55.40 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 53.30 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 20.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 129.00 us total DB time · 3 events
entity
orders.customer_id = 56
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 53.10 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 53.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 22.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 128.40 us total DB time · 3 events
entity
orders.customer_id = 79
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 49.80 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 49.40 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 29.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 125.70 us total DB time · 3 events
entity
orders.customer_id = 83
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 51.80 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 50.70 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 23.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 125.30 us total DB time · 3 events
entity
orders.customer_id = 97
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 54.10 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 52.70 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 18.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 123.10 us total DB time · 3 events
entity
orders.customer_id = 57
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 58.30 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 52.90 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 11.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 122.60 us total DB time · 3 events
entity
orders.customer_id = 70
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 50.90 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 50.30 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 21.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 122.40 us total DB time · 3 events
entity
orders.customer_id = 90
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 51.00 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 48.60 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 22.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 120.90 us total DB time · 3 events
entity
orders.customer_id = 75
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 52.00 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 49.90 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 19.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 120.60 us total DB time · 3 events
entity
orders.customer_id = 77
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 51.20 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 50.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 19.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 120.50 us total DB time · 3 events
entity
orders.customer_id = 86
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 50.60 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 50.30 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 19.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 120.40 us total DB time · 3 events
entity
orders.customer_id = 95
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 49.80 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 49.60 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 21.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 120.30 us total DB time · 3 events
entity
orders.customer_id = 89
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 52.70 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 48.90 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 18.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 120.10 us total DB time · 3 events
entity
orders.customer_id = 76
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 50.30 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 49.80 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 20.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 120.10 us total DB time · 3 events
entity
orders.customer_id = 87
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 51.50 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 49.70 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 18.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 120.10 us total DB time · 3 events
entity
orders.customer_id = 88
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 50.10 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 49.10 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 20.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 119.80 us total DB time · 3 events
entity
orders.customer_id = 81
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 50.50 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 50.30 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 19.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 119.50 us total DB time · 3 events
entity
orders.customer_id = 78
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 55.80 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 51.70 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 12.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 118.90 us total DB time · 3 events
entity
orders.customer_id = 91
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 49.90 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 49.10 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 19.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 117.20 us total DB time · 3 events
entity
orders.customer_id = 93
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 49.30 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 49.00 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 18.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 117.00 us total DB time · 2 events
entity
orders.id = 48
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 62.80 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 54.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 115.70 us total DB time · 3 events
entity
orders.customer_id = 92
operation
monthly-reconciliation
touched by
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 52.10 us
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 50.30 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 13.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 114.50 us total DB time · 3 events
entity
orders.customer_id = 99
operation
monthly-reconciliation
touched by
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 1× · 51.60 us
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 1× · 51.40 us
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 1× · 11.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 113.00 us total DB time · 2 events
entity
orders.id = 157
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 66.70 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 46.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 107.10 us total DB time · 2 events
entity
customers.id = 1
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 71.60 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 35.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 106.20 us total DB time · 2 events
entity
orders.id = 35
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 60.20 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 46.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 105.50 us total DB time · 2 events
entity
orders.id = 131
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 55.70 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 49.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 103.60 us total DB time · 2 events
entity
orders.id = 92
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 61.80 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 41.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 101.00 us total DB time · 2 events
entity
orders.id = 74
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 58.80 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 42.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 97.90 us total DB time · 2 events
entity
orders.id = 22
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 59.10 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 38.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 97.80 us total DB time · 2 events
entity
customers.id = 8
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 66.50 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 31.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 97.40 us total DB time · 2 events
entity
orders.id = 66
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 58.70 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 38.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 96.80 us total DB time · 3 events
entity
customers.id = 54
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 62.00 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 24.20 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 10.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 96.50 us total DB time · 2 events
entity
customers.id = 1
operation
complete-checkout
touched by
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 76.20 us
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 20.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 95.10 us total DB time · 2 events
entity
customers.id = 124
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 77.10 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 18.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 94.90 us total DB time · 2 events
entity
customers.id = 154
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 55.30 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 39.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 94.60 us total DB time · 2 events
entity
orders.id = 40
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 52.70 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 41.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 92.90 us total DB time · 2 events
entity
customers.id = 175
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 65.00 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 27.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 92.30 us total DB time · 2 events
entity
customers.id = 58
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 79.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 92.10 us total DB time · 2 events
entity
orders.id = 118
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 50.00 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 42.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 89.40 us total DB time · 2 events
entity
orders.id = 14
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 46.10 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 43.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 87.60 us total DB time · 2 events
entity
orders.id = 196
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 47.20 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 40.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 87.40 us total DB time · 2 events
entity
orders.id = 183
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 47.40 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 40.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 85.80 us total DB time · 2 events
entity
orders.id = 27
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 47.00 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 38.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 85.70 us total DB time · 2 events
entity
orders.id = 61
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 45.10 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 40.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 83.40 us total DB time · 2 events
entity
orders.id = 87
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 44.20 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 39.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 83.10 us total DB time · 2 events
entity
orders.id = 144
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 43.50 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 39.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 83.00 us total DB time · 2 events
entity
orders.id = 105
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 41.80 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 41.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 82.80 us total DB time · 2 events
entity
orders.id = 100
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 42.10 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 40.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 82.50 us total DB time · 2 events
entity
orders.id = 53
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 42.40 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 40.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 82.50 us total DB time · 2 events
entity
customers.id = 141
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 63.90 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 18.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 82.40 us total DB time · 2 events
entity
customers.id = 56
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 43.30 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 39.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 82.00 us total DB time · 2 events
entity
orders.id = 113
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 43.70 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 38.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 81.80 us total DB time · 2 events
entity
orders.id = 170
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 42.30 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 39.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 81.60 us total DB time · 2 events
entity
orders.id = 9
operation
finalize-shipment
touched by
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 41.70 us
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 39.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 81.50 us total DB time · 2 events
entity
customers.id = 127
operation
complete-checkout
touched by
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 61.50 us
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 20.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 81.20 us total DB time · 2 events
entity
orders.id = 79
operation
finalize-shipment
touched by
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 1× · 40.90 us
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 1× · 40.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 80.20 us total DB time · 2 events
entity
customers.id = 49
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 67.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 79.90 us total DB time · 2 events
entity
customers.id = 1
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 51.70 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 28.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 79.60 us total DB time · 3 events
entity
customers.id = 39
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 55.60 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 15.70 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 79.50 us total DB time · 3 events
entity
customers.id = 19
operation
post-master-update
touched by
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 46.40 us
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.50 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 78.90 us total DB time · 2 events
entity
customers.id = 90
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 60.70 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 18.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 77.40 us total DB time · 2 events
entity
customers.id = 192
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 55.20 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 22.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 77.20 us total DB time · 3 events
entity
customers.id = 9
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 35.50 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 32.20 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 9.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 77.00 us total DB time · 3 events
entity
customers.id = 42
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 52.90 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 15.60 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 76.10 us total DB time · 2 events
entity
customers.id = 36
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 41.80 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 34.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 72.70 us total DB time · 2 events
entity
customers.id = 158
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 54.60 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 18.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 72.60 us total DB time · 2 events
entity
customers.id = 38
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 59.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 71.50 us total DB time · 3 events
entity
customers.id = 5
operation
post-master-update
touched by
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 36.60 us
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 25.60 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 9.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 71.00 us total DB time · 2 events
entity
customers.id = 18
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 47.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 23.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 71.00 us total DB time · 2 events
entity
customers.id = 52
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 44.50 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 26.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 71.00 us total DB time · 2 events
entity
customers.id = 103
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 45.10 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 25.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 70.70 us total DB time · 2 events
entity
customers.id = 188
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 50.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 20.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 70.50 us total DB time · 3 events
entity
customers.id = 2
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 31.40 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 20.50 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 18.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 69.50 us total DB time · 3 events
entity
customers.id = 16
operation
post-master-update
touched by
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 29.90 us
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.90 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 14.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 69.10 us total DB time · 2 events
entity
customers.id = 73
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 52.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 16.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 69.00 us total DB time · 3 events
entity
customers.id = 34
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 45.00 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 15.90 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 69.00 us total DB time · 2 events
entity
customers.id = 107
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 51.70 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 17.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 67.60 us total DB time · 2 events
entity
customers.id = 71
operation
complete-checkout
touched by
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 35.30 us
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 32.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 67.40 us total DB time · 2 events
entity
customers.id = 26
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 54.70 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 67.00 us total DB time · 2 events
entity
customers.id = 3
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 42.90 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 24.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 66.80 us total DB time · 3 events
entity
customers.id = 22
operation
post-master-update
touched by
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 28.30 us
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 23.70 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 14.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 66.70 us total DB time · 2 events
entity
customers.id = 57
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 53.70 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 66.30 us total DB time · 3 events
entity
customers.id = 10
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 39.40 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 16.70 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 10.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 65.10 us total DB time · 3 events
entity
customers.id = 14
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 30.20 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 25.30 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 9.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 64.50 us total DB time · 3 events
entity
customers.id = 40
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 42.70 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 14.00 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 64.50 us total DB time · 3 events
entity
customers.id = 49
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 34.00 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 22.80 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 64.40 us total DB time · 2 events
entity
customers.id = 39
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 48.20 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 16.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 64.30 us total DB time · 2 events
entity
customers.id = 86
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 45.30 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 19.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 63.80 us total DB time · 3 events
entity
customers.id = 6
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 27.30 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 26.10 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 10.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 63.60 us total DB time · 3 events
entity
customers.id = 12
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 38.30 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 16.40 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 63.50 us total DB time · 2 events
entity
customers.id = 171
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 44.80 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 18.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 63.10 us total DB time · 3 events
entity
customers.id = 45
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 40.90 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 14.00 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 63.00 us total DB time · 2 events
entity
customers.id = 5
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 42.60 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 20.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 62.50 us total DB time · 2 events
entity
customers.id = 35
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 45.00 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 17.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 61.00 us total DB time · 2 events
entity
customers.id = 69
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 43.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 17.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 60.90 us total DB time · 3 events
entity
customers.id = 36
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 38.60 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 14.20 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 60.80 us total DB time · 2 events
entity
customers.id = 5
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 43.30 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 17.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 60.30 us total DB time · 3 events
entity
customers.id = 11
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 31.60 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 18.10 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 10.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 60.30 us total DB time · 3 events
entity
customers.id = 27
operation
post-master-update
touched by
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 27.50 us
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.70 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 60.00 us total DB time · 2 events
entity
customers.id = 9
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 42.20 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 17.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 59.90 us total DB time · 2 events
entity
customers.id = 6
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 46.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 59.90 us total DB time · 2 events
entity
customers.id = 53
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 47.50 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 59.80 us total DB time · 2 events
entity
customers.id = 29
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 46.90 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 59.70 us total DB time · 2 events
entity
customers.id = 137
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 42.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 17.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 59.60 us total DB time · 2 events
entity
customers.id = 9
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 46.60 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 59.50 us total DB time · 3 events
entity
customers.id = 25
operation
post-master-update
touched by
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 26.00 us
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.40 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 9.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 59.50 us total DB time · 2 events
entity
customers.id = 120
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 42.70 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 16.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 59.30 us total DB time · 3 events
entity
customers.id = 7
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 29.70 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 20.00 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 9.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 59.10 us total DB time · 3 events
entity
customers.id = 53
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 35.20 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 16.30 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 58.80 us total DB time · 2 events
entity
customers.id = 169
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 38.50 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 20.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 58.40 us total DB time · 2 events
entity
customers.id = 22
operation
update-profile
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 41.80 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 16.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 57.30 us total DB time · 2 events
entity
customers.id = 25
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 41.80 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 15.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 57.00 us total DB time · 3 events
entity
customers.id = 32
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.70 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 24.60 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 56.80 us total DB time · 2 events
entity
customers.id = 47
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 39.30 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 17.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 56.30 us total DB time · 2 events
entity
customers.id = 39
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 42.20 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 14.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 56.20 us total DB time · 3 events
entity
customers.id = 4
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 28.60 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 17.80 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 9.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 55.60 us total DB time · 2 events
entity
customers.id = 2
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 40.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 15.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 55.50 us total DB time · 3 events
entity
customers.id = 56
operation
post-master-update
touched by
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 24.90 us
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 22.90 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 55.50 us total DB time · 2 events
entity
customers.id = 50
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 35.60 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 19.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 55.30 us total DB time · 2 events
entity
customers.id = 22
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 43.50 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 11.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 55.20 us total DB time · 2 events
entity
customers.id = 16
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 42.70 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 55.20 us total DB time · 2 events
entity
customers.id = 44
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 36.90 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 18.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 54.90 us total DB time · 3 events
entity
customers.id = 21
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.70 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 21.80 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 54.80 us total DB time · 3 events
entity
customers.id = 26
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 25.70 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 20.60 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 54.40 us total DB time · 2 events
entity
customers.id = 85
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 29.20 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 25.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 54.30 us total DB time · 3 events
entity
customers.id = 43
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 33.20 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 13.50 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 54.20 us total DB time · 2 events
entity
customers.id = 13
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 41.10 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 54.10 us total DB time · 3 events
entity
customers.id = 44
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 32.80 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 13.80 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 53.90 us total DB time · 2 events
entity
customers.id = 35
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 39.50 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 14.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 53.60 us total DB time · 3 events
entity
customers.id = 52
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 23.50 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 21.70 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 53.30 us total DB time · 2 events
entity
customers.id = 28
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 41.00 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 52.90 us total DB time · 3 events
entity
customers.id = 13
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 28.40 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 15.70 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 52.90 us total DB time · 2 events
entity
customers.id = 22
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 31.90 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 21.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 52.70 us total DB time · 3 events
entity
customers.id = 8
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 25.90 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 16.30 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 10.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 52.70 us total DB time · 2 events
entity
customers.id = 60
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 40.10 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 52.50 us total DB time · 3 events
entity
customers.id = 3
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 25.80 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 16.90 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 9.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 52.50 us total DB time · 2 events
entity
customers.id = 19
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 40.70 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 11.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 51.90 us total DB time · 2 events
entity
customers.id = 99
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 30.00 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 21.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 51.60 us total DB time · 2 events
entity
customers.id = 56
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 39.80 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 11.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 51.10 us total DB time · 2 events
entity
customers.id = 20
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 37.90 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 51.00 us total DB time · 2 events
entity
customers.id = 59
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 36.90 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 14.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 50.80 us total DB time · 3 events
entity
customers.id = 29
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.00 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 18.00 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 50.60 us total DB time · 2 events
entity
customers.id = 11
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 37.10 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 50.50 us total DB time · 2 events
entity
customers.id = 78
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 26.90 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 23.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 50.50 us total DB time · 2 events
entity
customers.id = 41
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 36.60 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 50.40 us total DB time · 3 events
entity
customers.id = 28
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 25.10 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 16.90 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 50.40 us total DB time · 3 events
entity
customers.id = 46
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 25.30 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 16.10 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 9.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 50.10 us total DB time · 2 events
entity
customers.id = 4
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 36.90 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 49.80 us total DB time · 2 events
entity
customers.id = 50
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 36.50 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 49.70 us total DB time · 2 events
entity
customers.id = 37
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 37.80 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 11.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 49.70 us total DB time · 2 events
entity
customers.id = 43
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 36.30 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 49.60 us total DB time · 2 events
entity
customers.id = 31
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 37.50 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 49.50 us total DB time · 2 events
entity
customers.id = 7
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 36.30 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 49.40 us total DB time · 2 events
entity
customers.id = 29
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 27.90 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 21.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 49.40 us total DB time · 2 events
entity
customers.id = 10
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 36.70 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 49.40 us total DB time · 2 events
entity
customers.id = 17
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.90 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 49.30 us total DB time · 3 events
entity
customers.id = 55
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.70 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 13.40 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 11.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 49.20 us total DB time · 3 events
entity
customers.id = 38
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 28.30 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 12.90 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 49.20 us total DB time · 2 events
entity
customers.id = 113
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 28.20 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 21.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 49.20 us total DB time · 2 events
entity
customers.id = 32
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 36.00 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 49.10 us total DB time · 2 events
entity
customers.id = 27
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.90 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 49.00 us total DB time · 3 events
entity
customers.id = 18
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.90 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 15.30 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 49.00 us total DB time · 2 events
entity
customers.id = 12
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 36.80 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.90 us total DB time · 2 events
entity
customers.id = 52
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 36.30 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 48.70 us total DB time · 3 events
entity
customers.id = 17
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 25.30 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 15.30 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.70 us total DB time · 2 events
entity
customers.id = 15
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 26.50 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 22.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.70 us total DB time · 2 events
entity
customers.id = 21
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.90 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.60 us total DB time · 2 events
entity
customers.id = 14
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.50 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 48.50 us total DB time · 3 events
entity
customers.id = 15
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.60 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 15.30 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.50 us total DB time · 2 events
entity
customers.id = 23
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.50 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.40 us total DB time · 2 events
entity
customers.id = 36
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.40 us total DB time · 2 events
entity
customers.id = 45
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.50 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.40 us total DB time · 2 events
entity
customers.id = 48
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.30 us total DB time · 2 events
entity
customers.id = 8
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.70 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.30 us total DB time · 2 events
entity
customers.id = 30
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.60 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.30 us total DB time · 2 events
entity
customers.id = 51
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 36.10 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 48.10 us total DB time · 3 events
entity
customers.id = 20
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.90 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 14.70 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 48.00 us total DB time · 3 events
entity
customers.id = 35
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.90 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 14.70 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.00 us total DB time · 2 events
entity
customers.id = 15
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.70 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.00 us total DB time · 2 events
entity
customers.id = 24
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.00 us total DB time · 2 events
entity
customers.id = 33
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.40 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 48.00 us total DB time · 2 events
entity
customers.id = 54
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.00 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 47.90 us total DB time · 2 events
entity
customers.id = 18
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.80 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 47.80 us total DB time · 2 events
entity
customers.id = 34
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 35.30 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.50 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 47.80 us total DB time · 2 events
entity
customers.id = 40
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 34.60 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.20 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 47.80 us total DB time · 2 events
entity
customers.id = 55
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 34.90 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 12.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 47.30 us total DB time · 3 events
entity
customers.id = 41
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.30 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 12.90 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 10.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 47.30 us total DB time · 2 events
entity
customers.id = 42
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 34.20 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 13.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 47.10 us total DB time · 3 events
entity
customers.id = 31
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 23.80 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 14.30 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 9.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 46.70 us total DB time · 2 events
entity
customers.id = 46
operation
migrate-timezone
touched by
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 1× · 34.80 us
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 1× · 11.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 46.60 us total DB time · 2 events
entity
customers.id = 43
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 26.20 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 20.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 46.20 us total DB time · 3 events
entity
customers.id = 23
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.20 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 14.20 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 46.10 us total DB time · 2 events
entity
customers.id = 134
operation
complete-checkout
touched by
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 26.10 us
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 20.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 45.90 us total DB time · 2 events
entity
customers.id = 57
operation
complete-checkout
touched by
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 23.90 us
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 22.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 45.50 us total DB time · 3 events
entity
customers.id = 37
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 24.20 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 13.00 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 44.90 us total DB time · 3 events
entity
customers.id = 24
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 23.50 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 14.00 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 44.90 us total DB time · 3 events
entity
customers.id = 30
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 23.70 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 13.60 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 44.80 us total DB time · 3 events
entity
customers.id = 33
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 23.40 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 14.00 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 44.80 us total DB time · 3 events
entity
customers.id = 50
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 23.50 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 13.40 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 44.00 us total DB time · 3 events
entity
customers.id = 58
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 22.00 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 13.00 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 9.00 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 43.80 us total DB time · 3 events
entity
customers.id = 57
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 22.20 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 12.90 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 43.60 us total DB time · 2 events
entity
customers.id = 64
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 22.20 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 21.40 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 43.40 us total DB time · 3 events
entity
customers.id = 48
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 22.50 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 13.30 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 43.30 us total DB time · 3 events
entity
customers.id = 51
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 22.40 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 13.20 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 42.90 us total DB time · 3 events
entity
customers.id = 60
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 22.10 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 12.70 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 8.10 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 42.80 us total DB time · 3 events
entity
customers.id = 47
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 22.70 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 12.80 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.30 us
suggestion
Fetch all columns once and pass the row through the call chain.
3 templates 42.50 us total DB time · 3 events
entity
customers.id = 59
operation
post-master-update
touched by
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 1× · 21.70 us
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 1× · 13.00 us
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 1× · 7.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 40.90 us total DB time · 2 events
entity
customers.id = 106
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 23.20 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 17.70 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 40.20 us total DB time · 2 events
entity
customers.id = 155
operation
complete-checkout
touched by
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 22.30 us
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 17.90 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 38.70 us total DB time · 2 events
entity
customers.id = 120
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 21.10 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 17.60 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 36.10 us total DB time · 2 events
entity
customers.id = 141
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 19.30 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 16.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 35.60 us total DB time · 2 events
entity
customers.id = 148
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 18.80 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 16.80 us
suggestion
Fetch all columns once and pass the row through the call chain.
2 templates 35.60 us total DB time · 2 events
entity
customers.id = 162
operation
complete-checkout
touched by
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 1× · 18.80 us
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 1× · 16.80 us
suggestion
Fetch all columns once and pass the row through the call chain.

SELECT followed by UPDATE on the same row

READ → WRITE 133.00 us total · 1.87 ms app time between
entity
customers.id = 1
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 107.10 us total · 854.00 us app time between
entity
customers.id = 1
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 95.10 us total · 29.70 us app time between
entity
customers.id = 124
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 94.90 us total · 45.80 us app time between
entity
customers.id = 154
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 92.90 us total · 29.10 us app time between
entity
customers.id = 175
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 92.30 us total · 28.40 us app time between
entity
customers.id = 58
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 82.50 us total · 32.90 us app time between
entity
customers.id = 141
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 82.40 us total · 29.50 us app time between
entity
customers.id = 56
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 80.20 us total · 26.40 us app time between
entity
customers.id = 49
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 79.90 us total · 91.50 us app time between
entity
customers.id = 1
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 78.90 us total · 28.10 us app time between
entity
customers.id = 90
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 77.40 us total · 29.30 us app time between
entity
customers.id = 192
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 72.70 us total · 29.30 us app time between
entity
customers.id = 158
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 72.60 us total · 27.80 us app time between
entity
customers.id = 38
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 72.60 us total · 33.20 us app time between
entity
customers.id = 54
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 71.00 us total · 36.80 us app time between
entity
customers.id = 18
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 71.00 us total · 30.90 us app time between
entity
customers.id = 52
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 71.00 us total · 28.80 us app time between
entity
customers.id = 103
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 70.70 us total · 31.90 us app time between
entity
customers.id = 188
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 69.10 us total · 28.40 us app time between
entity
customers.id = 73
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 69.00 us total · 41.00 us app time between
entity
customers.id = 107
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 67.40 us total · 27.80 us app time between
entity
customers.id = 26
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 67.00 us total · 28.10 us app time between
entity
customers.id = 3
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 66.70 us total · 26.60 us app time between
entity
customers.id = 57
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 64.40 us total · 27.90 us app time between
entity
customers.id = 39
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 64.30 us total · 37.70 us app time between
entity
customers.id = 86
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 63.90 us total · 22.10 us app time between
entity
customers.id = 39
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 63.50 us total · 30.40 us app time between
entity
customers.id = 171
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 63.00 us total · 28.00 us app time between
entity
customers.id = 5
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 62.50 us total · 29.10 us app time between
entity
customers.id = 35
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 61.40 us total · 22.40 us app time between
entity
customers.id = 42
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 61.00 us total · 30.00 us app time between
entity
customers.id = 69
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 60.80 us total · 29.70 us app time between
entity
customers.id = 5
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 60.00 us total · 29.00 us app time between
entity
customers.id = 9
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 59.90 us total · 29.10 us app time between
entity
customers.id = 6
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 59.90 us total · 33.30 us app time between
entity
customers.id = 53
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 59.80 us total · 27.50 us app time between
entity
customers.id = 29
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 59.70 us total · 27.90 us app time between
entity
customers.id = 137
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 59.60 us total · 26.50 us app time between
entity
customers.id = 9
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 59.50 us total · 28.10 us app time between
entity
customers.id = 120
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 58.40 us total · 28.30 us app time between
entity
customers.id = 22
operation
update-profile
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 57.30 us total · 27.50 us app time between
entity
customers.id = 25
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 56.80 us total · 27.90 us app time between
entity
customers.id = 47
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 56.30 us total · 41.30 us app time between
entity
customers.id = 39
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 55.60 us total · 28.30 us app time between
entity
customers.id = 2
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 55.30 us total · 26.90 us app time between
entity
customers.id = 22
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 55.20 us total · 27.00 us app time between
entity
customers.id = 16
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 55.20 us total · 28.10 us app time between
entity
customers.id = 44
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 54.20 us total · 27.10 us app time between
entity
customers.id = 13
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 53.90 us total · 30.80 us app time between
entity
customers.id = 35
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 53.30 us total · 27.00 us app time between
entity
customers.id = 28
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 53.10 us total · 22.10 us app time between
entity
customers.id = 34
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 52.70 us total · 27.70 us app time between
entity
customers.id = 60
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 52.50 us total · 28.20 us app time between
entity
customers.id = 19
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 52.00 us total · 23.60 us app time between
entity
customers.id = 22
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 51.60 us total · 32.10 us app time between
entity
customers.id = 56
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 51.10 us total · 27.40 us app time between
entity
customers.id = 20
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 51.00 us total · 33.40 us app time between
entity
customers.id = 59
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 50.60 us total · 26.80 us app time between
entity
customers.id = 11
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 50.50 us total · 32.90 us app time between
entity
customers.id = 41
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 50.50 us total · 22.30 us app time between
entity
customers.id = 40
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 50.10 us total · 33.10 us app time between
entity
customers.id = 4
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 50.00 us total · 27.00 us app time between
entity
customers.id = 2
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 49.80 us total · 31.80 us app time between
entity
customers.id = 50
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 49.70 us total · 26.90 us app time between
entity
customers.id = 37
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 49.70 us total · 27.50 us app time between
entity
customers.id = 43
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 49.60 us total · 27.40 us app time between
entity
customers.id = 31
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 49.60 us total · 24.10 us app time between
entity
customers.id = 10
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 49.50 us total · 33.40 us app time between
entity
customers.id = 7
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 49.40 us total · 32.30 us app time between
entity
customers.id = 10
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 49.40 us total · 26.80 us app time between
entity
customers.id = 17
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 49.20 us total · 28.10 us app time between
entity
customers.id = 32
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 49.10 us total · 27.00 us app time between
entity
customers.id = 27
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 49.10 us total · 22.80 us app time between
entity
customers.id = 45
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 49.00 us total · 27.30 us app time between
entity
customers.id = 12
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.90 us total · 30.10 us app time between
entity
customers.id = 52
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.70 us total · 26.70 us app time between
entity
customers.id = 21
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.60 us total · 26.50 us app time between
entity
customers.id = 14
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.50 us total · 26.80 us app time between
entity
customers.id = 23
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.40 us total · 27.20 us app time between
entity
customers.id = 36
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.40 us total · 26.00 us app time between
entity
customers.id = 45
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.40 us total · 26.90 us app time between
entity
customers.id = 48
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.30 us total · 26.90 us app time between
entity
customers.id = 8
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.30 us total · 26.50 us app time between
entity
customers.id = 30
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.30 us total · 26.90 us app time between
entity
customers.id = 51
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.00 us total · 27.00 us app time between
entity
customers.id = 15
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.00 us total · 26.50 us app time between
entity
customers.id = 24
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.00 us total · 27.00 us app time between
entity
customers.id = 33
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 48.00 us total · 28.60 us app time between
entity
customers.id = 54
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 47.90 us total · 26.70 us app time between
entity
customers.id = 18
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 47.80 us total · 26.90 us app time between
entity
customers.id = 34
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 47.80 us total · 26.90 us app time between
entity
customers.id = 40
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 47.80 us total · 26.80 us app time between
entity
customers.id = 55
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 47.30 us total · 26.80 us app time between
entity
customers.id = 42
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 47.20 us total · 23.30 us app time between
entity
customers.id = 12
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 46.70 us total · 26.70 us app time between
entity
customers.id = 46
operation
migrate-timezone
read
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41
write
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 46.70 us total · 22.20 us app time between
entity
customers.id = 36
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 45.00 us total · 23.90 us app time between
entity
customers.id = 9
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 42.80 us total · 22.20 us app time between
entity
customers.id = 53
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 42.20 us total · 23.30 us app time between
entity
customers.id = 11
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 41.70 us total · 22.50 us app time between
entity
customers.id = 49
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 40.80 us total · 25.10 us app time between
entity
customers.id = 43
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 40.30 us total · 22.70 us app time between
entity
customers.id = 44
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 39.80 us total · 30.40 us app time between
entity
customers.id = 14
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 39.60 us total · 24.40 us app time between
entity
customers.id = 16
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 39.30 us total · 24.10 us app time between
entity
customers.id = 7
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 38.40 us total · 23.80 us app time between
entity
customers.id = 4
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 37.70 us total · 24.30 us app time between
entity
customers.id = 6
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 37.20 us total · 24.00 us app time between
entity
customers.id = 13
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 36.40 us total · 24.20 us app time between
entity
customers.id = 8
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 36.30 us total · 22.30 us app time between
entity
customers.id = 38
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 35.90 us total · 23.80 us app time between
entity
customers.id = 55
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 35.60 us total · 24.20 us app time between
entity
customers.id = 3
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 34.90 us total · 23.80 us app time between
entity
customers.id = 5
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 34.40 us total · 23.00 us app time between
entity
customers.id = 41
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 34.30 us total · 22.20 us app time between
entity
customers.id = 46
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 34.20 us total · 23.30 us app time between
entity
customers.id = 26
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 33.70 us total · 23.40 us app time between
entity
customers.id = 18
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 33.50 us total · 24.10 us app time between
entity
customers.id = 25
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 33.50 us total · 23.20 us app time between
entity
customers.id = 28
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 33.40 us total · 35.70 us app time between
entity
customers.id = 17
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 33.40 us total · 25.40 us app time between
entity
customers.id = 20
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 33.30 us total · 22.40 us app time between
entity
customers.id = 35
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 33.20 us total · 24.30 us app time between
entity
customers.id = 15
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 33.10 us total · 26.00 us app time between
entity
customers.id = 19
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 33.10 us total · 22.70 us app time between
entity
customers.id = 21
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 32.80 us total · 25.90 us app time between
entity
customers.id = 27
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 32.80 us total · 21.70 us app time between
entity
customers.id = 29
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 32.80 us total · 23.20 us app time between
entity
customers.id = 31
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 32.50 us total · 23.10 us app time between
entity
customers.id = 37
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 32.40 us total · 22.10 us app time between
entity
customers.id = 32
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 32.00 us total · 23.90 us app time between
entity
customers.id = 23
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 31.90 us total · 23.80 us app time between
entity
customers.id = 52
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 31.40 us total · 22.20 us app time between
entity
customers.id = 50
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 31.30 us total · 22.90 us app time between
entity
customers.id = 30
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 31.00 us total · 22.20 us app time between
entity
customers.id = 58
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 30.90 us total · 22.30 us app time between
entity
customers.id = 24
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 30.90 us total · 23.00 us app time between
entity
customers.id = 57
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 30.80 us total · 22.40 us app time between
entity
customers.id = 33
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 30.60 us total · 23.10 us app time between
entity
customers.id = 56
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 30.20 us total · 22.70 us app time between
entity
customers.id = 60
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 30.10 us total · 21.60 us app time between
entity
customers.id = 48
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 30.10 us total · 26.60 us app time between
entity
customers.id = 51
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 30.00 us total · 22.20 us app time between
entity
customers.id = 47
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
READ → WRITE 29.50 us total · 22.40 us app time between
entity
customers.id = 59
operation
post-master-update
read
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93
write
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112
suggestion
Collapse into one UPDATE (with the read's conditions moved into its WHERE) or one UPDATE … RETURNING.
Call-sites
Call-siteDB timeCountTemplates
fi.vesas.jdbclens.sample.dao.OrderDao.insert:9116.15 ms2001
fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:5513.68 ms1001
fi.vesas.jdbclens.capture.CapturingPreparedStatement.executeBatch:30111.93 ms11
fi.vesas.jdbclens.sample.dao.CustomerDao.findById:149.55 ms2001
fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:658.35 ms1001
fi.vesas.jdbclens.sample.dao.OrderDao.insert:917.54 ms2001
fi.vesas.jdbclens.capture.CapturingStatement.emitExecuteUnknown:2037.25 ms11
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readNextDetail:1117.15 ms1581
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:667.03 ms11
fi.vesas.jdbclens.capture.CapturingStatement.emitExecuteUnknown:2035.90 ms11
fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readNextKey:795.64 ms601
fi.vesas.jdbclens.capture.CapturingStatement.emitExecuteUnknown:2034.91 ms11
fi.vesas.jdbclens.sample.dao.SettingsDao.getByKey:144.71 ms2001
fi.vesas.jdbclens.sample.service.OrderReportService.topCustomersBySpend:404.56 ms11
fi.vesas.jdbclens.sample.dao.OrderDao.updateAmount:1184.33 ms1001
fi.vesas.jdbclens.sample.dao.ProductDao.findByNameLike:203.22 ms11
fi.vesas.jdbclens.sample.dao.OrderDao.findLatestByCustomer:372.98 ms251
fi.vesas.jdbclens.sample.dao.OrderDao.findLatestByCustomer:372.94 ms1001
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readNextMaster:842.83 ms501
fi.vesas.jdbclens.sample.dao.AuditDao.log:142.72 ms251
fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:552.64 ms101
fi.vesas.jdbclens.sample.dao.BalanceDao.insert:512.59 ms1001
fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:802.53 ms1001
fi.vesas.jdbclens.sample.service.PurgeService.purgeProcessedOutboxEvents:212.45 ms11
fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:732.43 ms601
fi.vesas.jdbclens.sample.dao.OrderDao.markRefunded:472.36 ms251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:662.23 ms101
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:662.07 ms11
fi.vesas.jdbclens.capture.CapturingStatement.emitExecuteUnknown:2031.99 ms11
fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:1121.81 ms601
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:661.78 ms71
fi.vesas.jdbclens.sample.dao.OutboxDao.markSent:571.65 ms431
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:661.46 ms11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:661.45 ms301
fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:551.34 ms301
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.writeMasterBreak:1451.29 ms501
fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:731.28 ms251
fi.vesas.jdbclens.sample.dao.AuditDao.log:141.26 ms251
fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:1091.21 ms251
fi.vesas.jdbclens.sample.dao.AuditDao.log:141.20 ms431
fi.vesas.jdbclens.sample.dao.BalanceDao.findByCustomer:311.18 ms1001
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:661.16 ms2001
fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:1001.15 ms251
fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:1201.13 ms601
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:661.13 ms2001
fi.vesas.jdbclens.capture.CapturingConnection.commit:2021.06 ms251
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readDetailFields:1251.05 ms1081
fi.vesas.jdbclens.sample.dao.OutboxDao.enqueue:301.03 ms501
fi.vesas.jdbclens.sample.cobol.CodeLookupService.resolveCurrencyLabel:79990.40 us601
fi.vesas.jdbclens.sample.dao.AuditDao.log:14982.50 us301
fi.vesas.jdbclens.sample.dao.OutboxDao.markFailed:67951.20 us71
fi.vesas.jdbclens.sample.dao.AuditDao.log:14932.60 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66900.20 us11
fi.vesas.jdbclens.sample.cobol.CodeLookupService.resolveShippingLabel:99841.50 us601
fi.vesas.jdbclens.sample.dao.SessionDao.touchLastSeen:13827.60 us301
fi.vesas.jdbclens.capture.CapturingConnection.commit:202822.40 us11
fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41820.70 us601
fi.vesas.jdbclens.sample.dao.SettingsDao.getByKey:14816.50 us251
fi.vesas.jdbclens.sample.cobol.CodeLookupService.resolveStatusLabel:89811.60 us601
fi.vesas.jdbclens.sample.dao.OrderDao.insert:91793.70 us251
fi.vesas.jdbclens.capture.CapturingConnection.commit:202785.80 us601
fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14780.30 us251
fi.vesas.jdbclens.capture.CapturingStatement.emitExecuteUnknown:203772.50 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66724.10 us11
fi.vesas.jdbclens.sample.dao.SettingsDao.getByKey:14720.90 us251
fi.vesas.jdbclens.capture.CapturingStatement.emitExecuteUnknown:203688.50 us11
fi.vesas.jdbclens.capture.CapturingStatement.emitExecuteUnknown:203670.20 us11
fi.vesas.jdbclens.capture.CapturingStatement.emitExecuteUnknown:203665.90 us11
fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24662.10 us251
fi.vesas.jdbclens.sample.service.PaginatedExportService.fetchPage:42656.10 us111
fi.vesas.jdbclens.capture.CapturingStatement.emitExecuteUnknown:203601.70 us11
fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93577.50 us601
fi.vesas.jdbclens.capture.CapturingStatement.emitExecuteUnknown:203560.10 us11
fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41542.50 us251
fi.vesas.jdbclens.capture.CapturingPreparedStatement.executeBatch:301520.70 us11
fi.vesas.jdbclens.sample.cobol.CodeLookupService.readOrder:67517.30 us601
fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readMasterFields:98506.50 us501
fi.vesas.jdbclens.sample.dao.OrderDao.findRecent:20506.30 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66493.00 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66479.60 us11
fi.vesas.jdbclens.sample.dao.ProductDao.findByIds:44462.40 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66409.20 us2001
fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41403.90 us301
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66307.40 us111
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66285.50 us1581
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66275.40 us1001
fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41272.50 us101
fi.vesas.jdbclens.sample.dao.ProductDao.findByNameLike:20271.50 us11
fi.vesas.jdbclens.sample.dao.ProductDao.findByNameLike:20258.00 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66236.00 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66234.90 us601
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66226.90 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66220.20 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66219.30 us1001
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66192.10 us301
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66188.30 us1081
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66179.20 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66174.10 us501
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66173.70 us1001
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66166.90 us1001
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66164.60 us2001
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66161.70 us601
fi.vesas.jdbclens.capture.CapturingConnection.commit:202159.50 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66157.10 us601
fi.vesas.jdbclens.sample.cobol.CodeLookupService.seedCodes:33150.30 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66150.10 us1001
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66147.30 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66144.10 us1001
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66143.60 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66142.30 us601
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66138.80 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66131.70 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66130.40 us501
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66130.00 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66128.70 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66128.30 us601
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66127.90 us431
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66113.20 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66109.30 us431
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6698.20 us501
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6694.00 us301
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6693.40 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6687.70 us1001
fi.vesas.jdbclens.sample.dao.OrderDao.findRecent:2087.10 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6677.10 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6671.50 us301
fi.vesas.jdbclens.sample.dao.OutboxDao.listPending:4056.00 us11
fi.vesas.jdbclens.sample.cobol.CodeLookupService.seedCodes:3754.60 us11
fi.vesas.jdbclens.sample.cobol.CodeLookupService.seedCodes:3553.50 us11
fi.vesas.jdbclens.sample.service.PurgeService.trimAuditLog:2853.10 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6648.40 us601
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6644.90 us501
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6644.00 us601
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6636.70 us601
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6634.60 us601
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6632.70 us601
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6628.70 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6623.30 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6620.90 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6619.20 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6617.60 us251
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:6614.80 us101
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:668.50 us11
fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:665.80 us11
Templates
TemplateDB timeCountp50p99DistributionCall-sites
INSERT INTO orders (customer_id, amount) VALUES (?, ?)24.49 ms42545.50 us187.80 us6
SELECT COUNT(*) FROM orders WHERE customer_id = ?17.65 ms14059.30 us2.44 ms6
INSERT INTO customers (id, name, email, phone, address_line, city, state, postal_code, country, timezone) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)11.93 ms111.93 ms11.93 ms2
SELECT name FROM customers WHERE id = ?10.34 ms22539.30 us167.90 us4
SELECT MIN(ID) FROM CUSTOMERS WHERE ID > ?8.47 ms11063.30 us198.40 us4
SELECT SUM(amount) FROM orders WHERE customer_id = ?8.35 ms10076.60 us172.00 us2
CREATE TABLE orders (id INT AUTO_INCREMENT PRIMARY KEY, customer_id INT, amount DECIMAL(?,?), status VARCHAR(?), shipped_at TIMESTAMP, refunded BOOLEAN DEFAULT FALSE)7.25 ms17.25 ms7.25 ms1
SELECT MIN(ID) FROM ORDERS WHERE CUSTOMER_ID = ? AND ID > ?7.15 ms15844.70 us113.90 us2
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)7.09 ms14829.60 us175.40 us10
SELECT v FROM settings WHERE k = ?6.25 ms25019.40 us79.70 us6
SELECT id, amount FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 15.92 ms12530.00 us219.90 us4
CREATE TABLE settings (k VARCHAR(?) PRIMARY KEY, v VARCHAR(?))5.90 ms15.90 ms5.90 ms1
CREATE TABLE customers (id INT PRIMARY KEY, name VARCHAR(?), email VARCHAR(?), phone VARCHAR(?), address_line VARCHAR(?), city VARCHAR(?), state VARCHAR(?), postal_code VARCHAR(?), country VARCHAR(?), timezone VARCHAR(?))4.91 ms14.91 ms4.91 ms1
SELECT c.id, c.name, COUNT(o.id), SUM(o.amount) FROM orders o JOIN customers c ON c.id = o.customer_id GROUP BY c.id, c.name ORDER BY SUM(o.amount) DESC LIMIT ?4.56 ms14.56 ms4.56 ms2
UPDATE orders SET amount = ? WHERE id = ?4.33 ms10039.60 us75.70 us2
SELECT id, name, price FROM products WHERE name LIKE ?3.75 ms3271.50 us3.22 ms6
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ?3.70 ms8541.00 us77.10 us4
SELECT V FROM SETTINGS WHERE K = ?2.64 ms18012.60 us36.20 us6
INSERT INTO customer_balances (customer_id, orders_count, lifetime_spend, last_order_at, updated_at) VALUES (?, ?, ?, ?, ?)2.59 ms10020.40 us88.10 us2
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 12.53 ms10023.30 us59.40 us2
DELETE FROM outbox_events WHERE status = 'SENT' AND processed_at < ?2.45 ms12.45 ms2.45 ms2
UPDATE orders SET refunded = TRUE WHERE id = ?2.36 ms2578.90 us167.20 us2
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ?2.04 ms12513.10 us56.10 us8
INSERT INTO settings (k, v) VALUES (?, ?), (?, ?)1.99 ms11.99 ms1.99 ms1
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ?1.81 ms6025.10 us62.00 us2
UPDATE outbox_events SET status = 'SENT', processed_at = ? WHERE id = ?1.65 ms4331.90 us164.00 us2
SELECT ID, AMOUNT, STATUS FROM ORDERS WHERE ID = ?1.57 ms1688.60 us20.00 us4
INSERT INTO AUDIT (KIND, PAYLOAD, TS) VALUES (?, ?, ?)1.29 ms5021.20 us85.90 us2
UPDATE orders SET shipped_at = ? WHERE id = ?1.21 ms2546.30 us61.80 us2
SELECT customer_id, orders_count, lifetime_spend, last_order_at FROM customer_balances WHERE customer_id = ?1.18 ms1009.80 us44.60 us2
UPDATE orders SET status = ? WHERE id = ?1.15 ms2540.90 us96.20 us2
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ?1.13 ms6015.70 us46.40 us2
INSERT INTO outbox_events (kind, payload, status, created_at) VALUES (?, ?, 'PENDING', ?)1.03 ms5017.10 us96.10 us2
UPDATE outbox_events SET status = 'FAILED', attempts = attempts + 1, last_error = ? WHERE id = ?951.20 us733.10 us601.90 us2
UPDATE sessions SET last_seen = CURRENT_TIMESTAMP WHERE id = ?827.60 us3019.40 us88.60 us2
CREATE TABLE reconciliation_exceptions (id INT AUTO_INCREMENT PRIMARY KEY, customer_id INT, expected DECIMAL(?,?), actual DECIMAL(?,?), reason VARCHAR(?), detected_at TIMESTAMP)772.50 us1772.50 us772.50 us1
CREATE TABLE products (id INT AUTO_INCREMENT PRIMARY KEY, sku VARCHAR(?), name VARCHAR(?), category VARCHAR(?), price DECIMAL(?,?), stock_qty INT)688.50 us1688.50 us688.50 us1
CREATE TABLE audit (id INT AUTO_INCREMENT PRIMARY KEY, kind VARCHAR(?), payload VARCHAR(?), ts TIMESTAMP)670.20 us1670.20 us670.20 us1
CREATE TABLE outbox_events (id INT AUTO_INCREMENT PRIMARY KEY, kind VARCHAR(?), payload VARCHAR(?), status VARCHAR(?) DEFAULT ?, attempts INT DEFAULT ?, last_error VARCHAR(?), created_at TIMESTAMP, processed_at TIMESTAMP)665.90 us1665.90 us665.90 us1
SELECT email FROM customers WHERE id = ?662.10 us2521.90 us76.20 us2
SELECT id, name, email FROM customers LIMIT ? OFFSET ?656.10 us1153.60 us115.10 us2
CREATE TABLE sessions (id INT PRIMARY KEY, last_seen TIMESTAMP)601.70 us1601.70 us601.70 us1
SELECT id, customer_id FROM orders ORDER BY id DESC LIMIT ?593.40 us2506.30 us506.30 us4
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ?577.50 us608.50 us28.30 us2
CREATE TABLE customer_balances (customer_id INT PRIMARY KEY, orders_count INT, lifetime_spend DECIMAL(?,?), last_order_at TIMESTAMP, updated_at TIMESTAMP)560.10 us1560.10 us560.10 us1
INSERT INTO products (sku, name, category, price, stock_qty) VALUES (?, ?, ?, ?, ?)520.70 us1520.70 us520.70 us2
SELECT ID, NAME FROM CUSTOMERS WHERE ID = ?506.50 us509.30 us31.70 us2
SELECT id, name, price FROM products WHERE id IN (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)462.40 us1462.40 us462.40 us2
MERGE INTO SETTINGS (K, V) KEY(K) VALUES (?, ?)258.40 us354.60 us150.30 us4
SELECT id, kind, payload, attempts FROM outbox_events WHERE status = ? ORDER BY id LIMIT ?56.00 us156.00 us56.00 us2
SELECT COUNT(*) FROM audit53.10 us153.10 us53.10 us2
Table access — caching analysis

Every table touched in this recording with its readers and writers. Tables labelled read-only had no writes during capture — that makes them the cleanest cache candidates, but the label is only ever a lower bound on safety (writes outside the recording window stay invisible). For read/write tables, the writer call-site count is the number of places that need invalidation (or write-through) hooks. Source-scan is enabled: each row also shows static readers/writers seen in .java files. A badge means the source has writer sites that didn't run during this recording — the real answer to 'is it safe to cache?'.

orders 794 reads · · 13 reader sites · 7 writer sites · 9 ops · static: 8 readers / 5 writers
readers
SELECT MIN(ID) FROM ORDERS WHERE CUSTOMER_ID = ? AND ID > ? — fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readNextDetail:111 · 158×
SELECT ID, AMOUNT, STATUS FROM ORDERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readDetailFields:125 · 108×
SELECT id, amount FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.findLatestByCustomer:37 · 100×
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 100×
SELECT SUM(amount) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.sumAmountByCustomer:65 · 100×
SELECT shipped_at FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.latestOrderAtByCustomer:80 · 100×
SELECT ID, AMOUNT, STATUS FROM ORDERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CodeLookupService.readOrder:67 · 60×
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 30×
SELECT id, amount FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1 — fi.vesas.jdbclens.sample.dao.OrderDao.findLatestByCustomer:37 · 25×
SELECT COUNT(*) FROM orders WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.countByCustomer:55 · 10×
SELECT id, customer_id FROM orders ORDER BY id DESC LIMIT ? — fi.vesas.jdbclens.sample.dao.OrderDao.findRecent:20 · 1×
SELECT id, customer_id FROM orders ORDER BY id DESC LIMIT ? — fi.vesas.jdbclens.sample.dao.OrderDao.findRecent:20 · 1×
SELECT c.id, c.name, COUNT(o.id), SUM(o.amount) FROM orders o JOIN customers c ON c.id = o.customer_id GROUP BY c.id, c.name ORDER BY SUM(o.amount) DESC LIMIT ? — fi.vesas.jdbclens.sample.service.OrderReportService.topCustomersBySpend:40 · 1×
writers
INSERT INTO orders (customer_id, amount) VALUES (?, ?) — fi.vesas.jdbclens.sample.dao.OrderDao.insert:91 · 200×
INSERT INTO orders (customer_id, amount) VALUES (?, ?) — fi.vesas.jdbclens.sample.dao.OrderDao.insert:91 · 200×
UPDATE orders SET amount = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateAmount:118 · 100× · SET amount
INSERT INTO orders (customer_id, amount) VALUES (?, ?) — fi.vesas.jdbclens.sample.dao.OrderDao.insert:91 · 25×
UPDATE orders SET refunded = TRUE WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markRefunded:47 · 25× · SET refunded
UPDATE orders SET status = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.updateStatus:100 · 25× · SET status
UPDATE orders SET shipped_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OrderDao.markShipped:109 · 25× · SET shipped_at
static readers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\cobol\CodeLookupService.java:65 SELECT ID, AMOUNT, STATUS FROM ORDERS WHERE ID = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\cobol\MasterDetailMergeJob.java:108 SELECT MIN(ID) FROM ORDERS WHERE CUSTOMER_ID = ? AND ID > ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\cobol\MasterDetailMergeJob.java:123 SELECT ID, AMOUNT, STATUS FROM ORDERS WHERE ID = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OrderDao.java:18 SELECT id, customer_id FROM orders ORDER BY id DESC LIMIT ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OrderDao.java:35 SELECT id, amount FROM orders WHERE customer_id = ? ORDER BY id DESC LIMIT 1
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OrderDao.java:53 SELECT COUNT(*) FROM orders WHERE customer_id = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OrderDao.java:63 SELECT SUM(amount) FROM orders WHERE customer_id = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OrderDao.java:77 SELECT shipped_at FROM orders WHERE customer_id = ?
static writers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OrderDao.java:45 UPDATE orders SET refunded = TRUE WHERE id = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OrderDao.java:88 INSERT INTO orders (customer_id, amount) VALUES (?, ?)
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OrderDao.java:97 UPDATE orders SET status = ? WHERE id = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OrderDao.java:106 UPDATE orders SET shipped_at = ? WHERE id = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OrderDao.java:115 UPDATE orders SET amount = ? WHERE id = ?
suggestion
Writes are frequent or scattered across many call-sites. Caching this table is only worthwhile with a single write gateway; otherwise stale reads are likely.
customers 667 reads · · 14 reader sites · 4 writer sites · 9 ops · static: 8 readers / 3 writers
readers
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 200×
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 60×
SELECT MIN(ID) FROM CUSTOMERS WHERE ID > ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readNextKey:79 · 60×
SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.readMasterRecord:93 · 60×
SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.invalidKeyCheck:120 · 60×
SELECT MIN(ID) FROM CUSTOMERS WHERE ID > ? — fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readNextMaster:84 · 50×
SELECT ID, NAME FROM CUSTOMERS WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.readMasterFields:98 · 50×
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 30×
SELECT name FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findById:14 · 25×
SELECT email FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findEmailById:24 · 25×
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 25×
SELECT id, name, email FROM customers LIMIT ? OFFSET ? — fi.vesas.jdbclens.sample.service.PaginatedExportService.fetchPage:42 · 11×
SELECT id, name, email, phone, address_line, city, state, postal_code, country, timezone FROM customers WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.findFullById:41 · 10×
SELECT c.id, c.name, COUNT(o.id), SUM(o.amount) FROM orders o JOIN customers c ON c.id = o.customer_id GROUP BY c.id, c.name ORDER BY SUM(o.amount) DESC LIMIT ? — fi.vesas.jdbclens.sample.service.OrderReportService.topCustomersBySpend:40 · 1×
writers
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 60× · SET name, email, phone, address_line, city, state, postal_code, country, timezone
UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ? — fi.vesas.jdbclens.sample.cobol.CustomerMasterBatchJob.rewriteMasterRecord:112 · 60× · SET name, country
UPDATE customers SET name = ?, email = ?, phone = ?, address_line = ?, city = ?, state = ?, postal_code = ?, country = ?, timezone = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.CustomerDao.updateAll:73 · 25× · SET name, email, phone, address_line, city, state, postal_code, country, timezone
INSERT INTO customers (id, name, email, phone, address_line, city, state, postal_code, country, timezone) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) — fi.vesas.jdbclens.capture.CapturingPreparedStatement.executeBatch:301 · 1×
static readers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\cobol\CustomerMasterBatchJob.java:77 SELECT MIN(ID) FROM CUSTOMERS WHERE ID > ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\cobol\CustomerMasterBatchJob.java:91 SELECT ID, NAME, EMAIL, COUNTRY FROM CUSTOMERS WHERE ID = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\cobol\CustomerMasterBatchJob.java:118 SELECT COUNT(*) FROM CUSTOMERS WHERE ID = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\cobol\MasterDetailMergeJob.java:82 SELECT MIN(ID) FROM CUSTOMERS WHERE ID > ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\cobol\MasterDetailMergeJob.java:96 SELECT ID, NAME FROM CUSTOMERS WHERE ID = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\CustomerDao.java:12 SELECT name FROM customers WHERE id = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\CustomerDao.java:22 SELECT email FROM customers WHERE id = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\service\PaginatedExportService.java:39 SELECT id, name, email FROM customers LIMIT ? OFFSET ?
static writers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\cobol\CustomerMasterBatchJob.java:108 UPDATE CUSTOMERS SET NAME = ?, COUNTRY = ? WHERE ID = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\CustomerDao.java:60 UPDATE customers SET name = ?, email = ?, phone = ?,
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\CustomerDao.java:81 INSERT INTO customers (id, name, email, phone, address_line,
suggestion
Writes are frequent or scattered across many call-sites. Caching this table is only worthwhile with a single write gateway; otherwise stale reads are likely.
settings 430 reads · · 6 reader sites · 1 writer sites · 3 ops · static: 4 readers / 1 writers
readers
SELECT v FROM settings WHERE k = ? — fi.vesas.jdbclens.sample.dao.SettingsDao.getByKey:14 · 200×
SELECT V FROM SETTINGS WHERE K = ? — fi.vesas.jdbclens.sample.cobol.CodeLookupService.resolveCurrencyLabel:79 · 60×
SELECT V FROM SETTINGS WHERE K = ? — fi.vesas.jdbclens.sample.cobol.CodeLookupService.resolveStatusLabel:89 · 60×
SELECT V FROM SETTINGS WHERE K = ? — fi.vesas.jdbclens.sample.cobol.CodeLookupService.resolveShippingLabel:99 · 60×
SELECT v FROM settings WHERE k = ? — fi.vesas.jdbclens.sample.dao.SettingsDao.getByKey:14 · 25×
SELECT v FROM settings WHERE k = ? — fi.vesas.jdbclens.sample.dao.SettingsDao.getByKey:14 · 25×
writers
INSERT INTO settings (k, v) VALUES (?, ?), (?, ?) — fi.vesas.jdbclens.capture.CapturingStatement.emitExecuteUnknown:203 · 1×
static readers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\cobol\CodeLookupService.java:77 SELECT V FROM SETTINGS WHERE K = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\cobol\CodeLookupService.java:87 SELECT V FROM SETTINGS WHERE K = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\cobol\CodeLookupService.java:97 SELECT V FROM SETTINGS WHERE K = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\SettingsDao.java:12 SELECT v FROM settings WHERE k = ?
static writers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\Bootstrap.java:42 INSERT INTO settings (k, v) VALUES
suggestion
Read/write ratio favours a cache. Writes come from 1 call-site(s) — wire invalidation (or a write-through wrapper) at each, keyed by the columns shown in writer SET clauses.
customer_balances 100 reads · · 1 reader sites · 1 writer sites · 1 ops · static: 0 readers / 2 writers
readers
SELECT customer_id, orders_count, lifetime_spend, last_order_at FROM customer_balances WHERE customer_id = ? — fi.vesas.jdbclens.sample.dao.BalanceDao.findByCustomer:31 · 100×
writers
INSERT INTO customer_balances (customer_id, orders_count, lifetime_spend, last_order_at, updated_at) VALUES (?, ?, ?, ?, ?) — fi.vesas.jdbclens.sample.dao.BalanceDao.insert:51 · 100×
static writers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\BalanceDao.java:43 INSERT INTO customer_balances
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\BalanceDao.java:62 UPDATE customer_balances SET orders_count = ?,
suggestion
Writes are frequent or scattered across many call-sites. Caching this table is only worthwhile with a single write gateway; otherwise stale reads are likely.
products 4 reads · · 4 reader sites · 1 writer sites · 1 ops · static: 2 readers / 1 writers
readers
SELECT id, name, price FROM products WHERE name LIKE ? — fi.vesas.jdbclens.sample.dao.ProductDao.findByNameLike:20 · 1×
SELECT id, name, price FROM products WHERE name LIKE ? — fi.vesas.jdbclens.sample.dao.ProductDao.findByNameLike:20 · 1×
SELECT id, name, price FROM products WHERE name LIKE ? — fi.vesas.jdbclens.sample.dao.ProductDao.findByNameLike:20 · 1×
SELECT id, name, price FROM products WHERE id IN (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) — fi.vesas.jdbclens.sample.dao.ProductDao.findByIds:44 · 1×
writers
INSERT INTO products (sku, name, category, price, stock_qty) VALUES (?, ?, ?, ?, ?) — fi.vesas.jdbclens.capture.CapturingPreparedStatement.executeBatch:301 · 1×
static readers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\ProductDao.java:18 SELECT id, name, price FROM products WHERE name LIKE ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\ProductDao.java:40 SELECT id, name, price FROM products WHERE id IN (
static writers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\Bootstrap.java:88 INSERT INTO products (sku, name, category, price, stock_qty)
suggestion
Writes are frequent or scattered across many call-sites. Caching this table is only worthwhile with a single write gateway; otherwise stale reads are likely.
audit 1 reads · · 1 reader sites · 6 writer sites · 1 ops · static: 1 readers / 3 writers
readers
SELECT COUNT(*) FROM audit — fi.vesas.jdbclens.sample.service.PurgeService.trimAuditLog:28 · 1×
writers
INSERT INTO AUDIT (KIND, PAYLOAD, TS) VALUES (?, ?, ?) — fi.vesas.jdbclens.sample.cobol.MasterDetailMergeJob.writeMasterBreak:145 · 50×
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP) — fi.vesas.jdbclens.sample.dao.AuditDao.log:14 · 43×
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP) — fi.vesas.jdbclens.sample.dao.AuditDao.log:14 · 30×
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP) — fi.vesas.jdbclens.sample.dao.AuditDao.log:14 · 25×
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP) — fi.vesas.jdbclens.sample.dao.AuditDao.log:14 · 25×
INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP) — fi.vesas.jdbclens.sample.dao.AuditDao.log:14 · 25×
static readers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\service\PurgeService.java:27 SELECT COUNT(*) FROM audit
static writers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\cobol\MasterDetailMergeJob.java:139 INSERT INTO AUDIT (KIND, PAYLOAD, TS) VALUES (?, ?, ?)
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\AuditDao.java:11 INSERT INTO audit (kind, payload, ts) VALUES (?, ?, CURRENT_TIMESTAMP)
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\service\PurgeService.java:37 DELETE FROM audit WHERE id IN (SELECT id FROM audit ORDER BY id LIMIT ?)
suggestion
Writes are frequent or scattered across many call-sites. Caching this table is only worthwhile with a single write gateway; otherwise stale reads are likely.
outbox_events 1 reads · · 1 reader sites · 4 writer sites · 1 ops · static: 1 readers / 4 writers
readers
SELECT id, kind, payload, attempts FROM outbox_events WHERE status = ? ORDER BY id LIMIT ? — fi.vesas.jdbclens.sample.dao.OutboxDao.listPending:40 · 1×
writers
INSERT INTO outbox_events (kind, payload, status, created_at) VALUES (?, ?, 'PENDING', ?) — fi.vesas.jdbclens.sample.dao.OutboxDao.enqueue:30 · 50×
UPDATE outbox_events SET status = 'SENT', processed_at = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OutboxDao.markSent:57 · 43× · SET status, processed_at
UPDATE outbox_events SET status = 'FAILED', attempts = attempts + 1, last_error = ? WHERE id = ? — fi.vesas.jdbclens.sample.dao.OutboxDao.markFailed:67 · 7× · SET status, attempts, last_error
DELETE FROM outbox_events WHERE status = 'SENT' AND processed_at < ? — fi.vesas.jdbclens.sample.service.PurgeService.purgeProcessedOutboxEvents:21 · 1×
static readers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OutboxDao.java:36 SELECT id, kind, payload, attempts FROM outbox_events
static writers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OutboxDao.java:25 INSERT INTO outbox_events (kind, payload, status, created_at)
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OutboxDao.java:53 UPDATE outbox_events SET status = 'SENT', processed_at = ?
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\OutboxDao.java:63 UPDATE outbox_events SET status = 'FAILED',
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\service\PurgeService.java:19 DELETE FROM outbox_events WHERE status = 'SENT' AND processed_at < ?
suggestion
Writes are frequent or scattered across many call-sites. Caching this table is only worthwhile with a single write gateway; otherwise stale reads are likely.
sessions 0 reads · · 0 reader sites · 1 writer sites · 0 ops · static: 0 readers / 1 writers
writers
UPDATE sessions SET last_seen = CURRENT_TIMESTAMP WHERE id = ? — fi.vesas.jdbclens.sample.dao.SessionDao.touchLastSeen:13 · 30× · SET last_seen
static writers
C:\p_drafts\jdbc-lens\sample-app\src\main\java\fi\vesas\jdbclens\sample\dao\SessionDao.java:11 UPDATE sessions SET last_seen = CURRENT_TIMESTAMP WHERE id = ?
suggestion
Writes are frequent or scattered across many call-sites. Caching this table is only worthwhile with a single write gateway; otherwise stale reads are likely.
Transactions

Every explicit transaction reconstructed from COMMIT / ROLLBACK boundaries. The overview gives the overall transaction shape of the workload; the table below lists the longest transactions by wall-clock time. Commit-per-record runs are flagged in their own findings section above.

explicit transactions
89
committed / rolled back / open
87 / 0 / 2
median wall-clock
264.20 us
p99 wall-clock
128.15 ms
total wall time inside TXs
3.18 s
total DB time inside TXs
35.46 ms
writes / reads inside TXs
112 / 205

Longest transactions

Top 20 explicit transactions by wall-clock duration. Useful for eyeballing outliers the detector did not otherwise flag.

operation thread wall DB writes reads outcome opening call-site
refund-latest 1 135.50 ms 632.90 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 128.15 ms 285.20 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 126.19 ms 304.30 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 126.11 ms 381.90 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 126.04 ms 545.60 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 125.38 ms 423.50 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 125.38 ms 525.70 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 125.37 ms 417.90 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 125.24 ms 321.10 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 125.08 ms 366.90 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 124.91 ms 332.10 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 124.70 ms 334.90 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 124.70 ms 496.60 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 124.62 ms 360.50 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 124.52 ms 328.00 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 124.36 ms 383.60 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 124.22 ms 381.40 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 124.19 ms 307.40 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 124.07 ms 373.80 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66
refund-latest 1 124.03 ms 472.70 us 2 1 commit fi.vesas.jdbclens.capture.CapturingConnection.wrapPrepared:66