[
https://issues.apache.org/jira/browse/LOG4NET-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570006#comment-17570006
]
Davyd McColl commented on LOG4NET-686:
--------------------------------------
[~pschulz] I looked at this today: 2.0.14 pretty-much does what your snippet
does (via community contribution on 2021-11-23 by Nikolay -
[https://github.com/apache/logging-log4net/commit/86fcc5397e2bdd72882c28bdeea10d61c30667a3]).
Are you 100% sure of the version and the fix?
currently in the codebase:
{color:#57a64a}/// <summary>
{color}{color:#57a64a}/// Prepare entire database command object to be executed.
{color}{color:#57a64a}/// </summary>
{color}{color:#57a64a}/// <param name="dbCmd">The command to prepare.</param>
{color}{color:#569cd6}protected virtual void
{color}{color:#dcdcaa}Prepare{color}{color:#e8ba36}({color}{color:#b8d7a3}IDbCommand
{color}{color:#9cdcfe}dbCmd{color}{color:#e8ba36})
{color}{
{color:#57a64a}// npgsql require parameters to prepare command
{color} {color:#569cd6}foreach
{color}{color:#e8ba36}({color}{color:#4ec9b0}AdoNetAppenderParameter
{color}{color:#9cdcfe}parameter {color}{color:#569cd6}in
{color}m_parameters{color:#e8ba36})
{color}{color:#e8ba36} {color}{color:#a952cb}{
{color}
{color:#9cdcfe}parameter{color}.{color:#dcdcaa}Prepare{color}{color:#e8ba36}({color}{color:#9cdcfe}dbCmd{color}{color:#e8ba36}){color};
{color:#a952cb}}
{color}{color:#a952cb}
{color}{color:#a952cb}
{color}{color:#9cdcfe}dbCmd{color}.{color:#dcdcaa}Prepare{color}{color:#e8ba36}(){color};
}
Would it be possible to share a project reproducing the issue?
> AdoNetAppender not working over SQL server
> ------------------------------------------
>
> Key: LOG4NET-686
> URL: https://issues.apache.org/jira/browse/LOG4NET-686
> Project: Log4net
> Issue Type: Bug
> Components: Builds
> Affects Versions: 2.0.14
> Environment: Windows 10 Pro N, 21H2
> .NET framework 4.7.1
> Reporter: Hugues Stefanski
> Priority: Major
> Attachments: Log4NetTest.zip
>
>
> Hello,
> Following an update of our dependencies, I noticed that my log traces are not
> getting output to SQL server anymore. I created a test project (attached to
> this issue), with the same configuration, using v2.0.12 and v2.0.14, and
> confirmed that 2.0.12 worked as expected, while 2.0.14 does not write
> anything.
>
> Checking the release notes, I stumbled on [PR
> 77|https://github.com/apache/logging-log4net/pull/77], which I guess might be
> related (but that's just a wild guess)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
