Opened 5 years ago
Closed 5 years ago
#1062 closed defect (fixed)
consider defaulting arraysize to 50 for oracle; at least provide an engine-level setting for it
| Reported by: | zzzeek | Owned by: | zzzeek |
|---|---|---|---|
| Priority: | medium | Milestone: | 0.4.xx |
| Component: | (none) | Severity: | no triage selected yet |
| Keywords: | Cc: | ||
| Progress State: | awaiting triage |
Description
this because cx_oracle performs much faster with it on. If no side effects occur for BLOBs (which I bet they do), it can be a default.
unfortunately it seems like the arraysize setting must be placed before the execute(), so we can't uniformly detect BLOBs and then set (since we dont really know until result time). this *may* be yet another candidate for connection-level options (but cx_oracle should really improve this).
Change History (1)
comment:1
Changed 5 years ago by zzzeek
- Milestone changed from 0.5.xx to 0.4.xx
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
this worked out well, in fact the result can have any number of BLOB/CLOB cursors opened inside of it, so the arraysize setting doesn't break it. It's when the *next* set of results are fetched that the previous cursors break. So in that sense if arraysize were always 50-100 here, we might not have noticed the need for BufferedColumnRow for a longer period of time. r0a35bf07f737 ra2540fc54d15.