Skip to content

eHive DBConnections don't allow hash access on the StatementHandle

Marek Szuba requested to merge github/fork/muffato/release/94 into release/94

Created by: muffato


eHive uses different encapsulation of DBI::st (containment rather than inheritance), meaning that the hash interface $sth->{Active} doesn't work. Instead we need to call dbi_sth() first. Alternatively, attributes like mysql_use_result can be passed to prepare().

Use case

In Compara we use eHive's DBConnections as 1) they can be constructed with an URL and 2) they are more resilient to database disconnections


With this change, SqlHelper compatible with eHive

Possible Drawbacks

If applicable, describe any possible undesirable consequence of the changes.


Have you added/modified unit tests to test the changes?

If so, do the tests pass/fail?

Have you run the entire test suite and no regression was detected?

Merge request reports