luciano/next-jdbc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add MySQL-specific streaming tip

Browse source
This commit is contained in:
Sean Corfield 2020-04-27 17:48:29 -07:00
parent d3f126145b
commit aa1c8a4cea
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/tips-and-tricks.md
View file

@ -89,6 +89,14 @@ MySQL generally stores tables as files so they are case-sensitive if your O/S is
It's also worth noting that column comparisons are case-insensitive so `WHERE foo = 'BAR'` will match `"bar"` or `"BAR"` etc.
### Streaming Result Sets
You should be able to get MySQL to stream very large result sets (when you are reducing over `plan`) by setting the following options:
* `:fetch-size Integer/MIN_VALUE` -- when running `plan` (or when creating a `PreparedStatement`).
> Note: it's possible that other options may be required as well -- I have not verified this yet -- see, for example, the additional options PostgreSQL requires, below.
## Oracle
Ah, dear old Oracle! Over the years of maintaining `clojure.java.jdbc` and now `next.jdbc`, I've had all sorts of bizarre and non-standard behavior reported from Oracle users. The main issue I'm aware of with `next.jdbc` is that Oracle's JDBC drivers all return an empty string from `ResultSetMetaData.getTableName()` so you won't get qualified keywords in the result set hash maps. Sorry!