Allow different connection string for run-time

[fsprojects]

Allow different connection string for run-time

[dsevastianov]

Where would you prefer to see it? I think it makes sense to have it on Execute, this way there is no need to repeat parameters for different connections.

[rojepp]

Sure, an optional param on Execute is fine. If you want to keep following what Sql TP is doing, you can do that too.
In that case, ditch the public constructor, and add the static GetDataContext() method for creating instances. That would also have the optional connstring param. Whichever way is fine with me.

[dsevastianov]

In the end, we decided to expose ConnectionString as property. This way it can be overridden right on constructor call. Does it make sense to you?

[rojepp]

@dsevastianov Sounds good, thanks!

[dmitry-a-morozov]

@rojepp I was thinking go back to your suggestion and make connectionString as optional ctor parameter for generated command class instead of property. It makes usage simpler and TP code cleaner. What do you think?

[rojepp]

Sounds good to me!
On Oct 22, 2013 3:46 PM, "Dmitry" [email protected] wrote:

@rojepp https://github.com/rojepp I was thinking go back to your
suggestion and make connectionString as optional ctor parameter for
generated command class instead of property. It makes usage simpler and TP
code cleaner. What do you think?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-26803795
.

[dmitry-a-morozov]

Connection string override as parameters to generate command type.