Vasiliy
Posts: 378
|
| Posted: 03/05/2007, 12:26 PM |
|
In some cases connection to DB requires seetting additional properties at run time, before execution.
For example, in my Application (.Net, MSSQL) I'm getting timeout errors on some SQL Insert/Update commands.
To solve the problem I have to edit file "CodeCharge.Data.MSSQL.vb", function ExecuteNonQueryImpl, which is not good.
Instead, I'd like to have an option to set a global connection property "CommandTimeout" in connection settings.
_________________
Vasiliy |
 |
 |
Benjamin Krajmalnik
|
| Posted: 03/05/2007, 5:25 PM |
|
I second that - great suggestion!
"Vasiliy" <Vasiliy@forum.codecharge> wrote in message
news:2245ec7d0d129b9@news.codecharge.com...
> In some cases connection to DB requires seetting additional properties at
> run
> time, before execution.
>
> For example, in my Application (.Net, MSSQL) I'm getting timeout errors on
> some
> SQL Insert/Update commands.
>
> To solve the problem I have to edit file "CodeCharge.Data.MSSQL.vb",
> function
> ExecuteNonQueryImpl, which is not good.
>
> Instead, I'd like to have an option to set a global connection property
> "CommandTimeout" in connection settings.
>
> _________________
> Vasiliy V Goncharenko
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
|
