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
I'm just wondering why the return value from the CreatePersistent overloads on Effort.DbConnectionFactory is DbConnection while the return value from CreateTransient is EffortConnection. I can see that (at least in my case) the return value from CreatePersistent is also an EffortConnection, so downcasting manually is possible, but why aren't the return types the same? Is the object returned from CreatePersistent sometimes not an EffortConnection?
The text was updated successfully, but these errors were encountered:
CreateTransient was originally returning a DbConnection but we modified it to EffortConnection since we added a few options on it.
I don't think there is any reason why CreatePersistent doesn't return yet an EffortConnection besides that we missed to do it when we have done the CreateTransient.
I'm just wondering why the return value from the
CreatePersistent
overloads on Effort.DbConnectionFactory isDbConnection
while the return value fromCreateTransient
isEffortConnection
. I can see that (at least in my case) the return value from CreatePersistent is also an EffortConnection, so downcasting manually is possible, but why aren't the return types the same? Is the object returned from CreatePersistent sometimes not an EffortConnection?The text was updated successfully, but these errors were encountered: