From @Jared314 on February 17, 2015 5:5
The NEventStore.Serialization.SqlPersistanceFactory constructor that accepts a database connection string name, automatically resolve the sql dialect if non is provided. But, the constructor that accepts an IConnectionFactory requires an explicit sql dialect. The IConnectionFactory interface contains a method to get the provider type information and could also automatically resolve the dialect.
I currently utilize IConnectionFactory to wrap custom database resolution logic, and had to implement custom dialect detection. Is the behavior difference intentional? Should I not be using the UsingSqlPersistence(IConnectionFactory factory) overload for wireup?
Copied from original issue: NEventStore/NEventStore#395
From @Jared314 on February 17, 2015 5:5
The
NEventStore.Serialization.SqlPersistanceFactoryconstructor that accepts a database connection string name, automatically resolve the sql dialect if non is provided. But, the constructor that accepts anIConnectionFactoryrequires an explicit sql dialect. TheIConnectionFactoryinterface contains a method to get the provider type information and could also automatically resolve the dialect.I currently utilize
IConnectionFactoryto wrap custom database resolution logic, and had to implement custom dialect detection. Is the behavior difference intentional? Should I not be using theUsingSqlPersistence(IConnectionFactory factory)overload for wireup?Copied from original issue: NEventStore/NEventStore#395