René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"SqlPersistanceFactory requires an explicit sql dialect when provided an IConnectionFactory","articleBody":"_From @Jared314 on February 17, 2015 5:5_\n\nThe `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.\n\nI 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?\n\n_Copied from original issue: NEventStore/NEventStore#395_\n","author":{"url":"https://github.com/kblooie","@type":"Person","name":"kblooie"},"datePublished":"2015-05-23T20:11:13.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/3/NEventStore.Persistence.SQL/issues/3"}