[CONJ-684] Performance of con.getMetaData().getProcedureColumns(null, null, name, "%") is much lower than mysql jdbc Created: 2019-02-20 Updated: 2019-09-17 |
|
| Status: | Confirmed |
| Project: | MariaDB Connector/J |
| Component/s: | metadata |
| Affects Version/s: | 1.7.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Xiao Peipei | Assignee: | Diego Dupin |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | mariadbjdbc, metadata, performance | ||
| Environment: |
SUSE11 |
||
| Issue Links: |
|
||||||||
| Description |
|
Recently, i use mariadb jdbc replace of mysql jdbc in our project. After replcing i found there is heavyer time costs of page reload in one of my forward app. To figure out why i has a below comparsion, i found it's the deal of the methond connection.getMetaData().getProcedureColumns(). |
| Comments |
| Comment by Diego Dupin [ 2019-03-14 ] |
|
Right, current implementation is fast only when not having lots of procedures/functions, and performance degrade fast when there is ! Implementation must rely on mysql.proc : Downside is that I_S tables are always accessible without any rights, mysql.proc needs some rights. MySQL default implementation rely on accessing mysql.proc (or if not set option "noAccessToProcedureBodies") |
| Comment by Diego Dupin [ 2019-09-17 ] |
|
This will be corrected by |