Pluggable is definitely better. A friend kept having to jump through a few
hoops to use his own PK generator with various adapters in the past.
On Tue, Mar 6, 2018 at 11:53 AM, Andrus Adamchik
wrote:
> I wish we could decouple a choice of PK generation strategy from the
> adapter. (I even thin
I wish we could decouple a choice of PK generation strategy from the adapter.
(I even think we have a task for this somewhere). Otherwise whatever we do with
this PR is going to be an issue for someone... E.g. if we keep the old one as
the default (which sounds sensible), then SQLServer2012Adapt
Hi all,
Need your advice. We have PR[1] that offers PK generator for SQL
Server, based on sequences with optional usage of NEWID() function for
char PKs.
The catch is that min version of SQLServer that supports this is 2012.
So my question is: can we upgrade default cayenne support to that
versio
