You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if you're using our master branch (1.4 pre-release) and you do like where it's heading please salt the project.
AR-JDBC 1.4.x releases aim to finally provide performance improvements that should much up the AR query execution time with MRI (and beyond). Historically optimization has not been done much as most of the time is spent hustling with AR compatibility and supported adapter variability. There's certainly a lot of room for improvement and for most production adapters such as MySQL, PostgreSQL the results should be noticeable. There's also plenty of refactoring (and maybe even some new features) to be done, that has been simply avoided on the 1.3 stable line.
performance improvements
try to resolve byte ruby String when possible
covert to ruby Time directly from native part
review adapters whether they really need binary/char stream reading
...
rewrite JDBCError (support cause compat with 2.1)
do not wrap runtime exceptions into JDBCErrors
allow for lazy JDBC connection initialization (should be default for JNDI)
support disabling configure_connection calls using a config value
try to log transaction begin/commit happening similar to core
review savepoint tracking (avoid map instantiation and/or use internal variable)
if you're using our master branch (1.4 pre-release) and you do like where it's heading please salt the project.
AR-JDBC 1.4.x releases aim to finally provide performance improvements that should much up the AR query execution time with MRI (and beyond). Historically optimization has not been done much as most of the time is spent hustling with AR compatibility and supported adapter variability. There's certainly a lot of room for improvement and for most production adapters such as MySQL, PostgreSQL the results should be noticeable. There's also plenty of refactoring (and maybe even some new features) to be done, that has been simply avoided on the 1.3 stable line.
configure_connection
calls using a config value:adapter_spec
if there's an adapter class:adapter_class
and pass it down as a jdbc_connection arge.g. oracle-enhanced does :
ArJdbc::MySQL::Column
patch log to print cause's error (maybe try Rails itself)debug
on (e.g. due "Returning autogenerated keys is not supported" error when running rails db:migrate #472)attr_writer :limit, :precision
inJdbcColumn
usesType(runtime)
if they're to stay!jndi:
configuration when using pool default size ?exec_proc
support ?:git
paths in Gemfile (.jar no longer commited)unescape_bytea
into native🍨 🍨 🍧
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: