Any plans for the cache_pks option take advantage of the tactical eager 
loading so it can do it in one fell swoop?
On Wednesday, July 1, 2020 at 7:49:48 AM UTC-7 Jeremy Evans wrote:

> Sequel 5.34.0 has been released!
>
> = New Features
>
> * The association_pks plugin now creates *_pks_dataset methods for
>   each association.  These are similar to the existing *_pks getter
>   methods, but they return a dataset of the keys instead of the keys
>   themselves.
>
> * The association_pks plugin now supports a :cache_pks association
>   option, which will cache calls to the *_pks getter method. The
>   default behavior remains that the *_pks getter method only returns
>   cached values if the *_pks= setter method has been used to set the
>   values.
>
> * The *_pks getter methods supported by the association_pks plugin
>   now support a :refresh option to ignore any cached values, similar
>   to how the association getter methods work.
>
> = Other Improvements
>
> * If trying to disconnect a server that doesn't exist when using a
>   sharded connection pool, a Sequel::Error is now raised.  Previously,
>   the sharded threaded pool raised a NoMethodError and the sharded
>   single connection pool did not raise an error.
>
> * If using the :savepoint option when savepoints are not supported,
>   a Sequel::InvalidOperation exception is now raised, instead of a
>   NoMethodError.
>
> * Calling Dataset#eager_graph with no arguments now returns the
>   dataset.
>
> * If not connected to the database, the single connection pool will
>   not yield any connections to Database#pool.all_connections.
>
> * Forcing a :ruby eager limit strategy for an association without a
>   limit or offset now works correctly.
>
> * Multiple unnecessary conditionals have been removed.
>
> * Sequel core and model code now have 100% branch coverage.
>
> Thanks,
> Jeremy
>

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sequel-talk/9888c87e-48af-47af-afc0-216284dc3c68n%40googlegroups.com.

Reply via email to