Utility class which will obtain the SQL for a query. DevForce does not generate SQL: it allows EF to do this, on the server, wwhen a DevForce query is reshaped as an ObjectQuery. Because of this, DevForce never really has the generated SQL, it must ask EF for it. To obtain the SQL here we're turning on a DevForce logging attribute, "ShouldLogSqlQueries", to allow SQL messages to be written by the DevForce trace publisher. We're then subscribing to the publisher and looking only for messages coming from a specific source. The publishing mechanism within DevForce runs on a separate thread, and pushes out all trace/debug messages. LINQPad needs the SQL for display purposes by the time the query has finished executing - which is a problem for us because the trace message may not have been published or received yet. To work around this, the driver will call here to pull the SQL message, with a short wait if necessary, instead of something more intuitive like using an event handler.
SqlLogger Class Documentation
Example #1
0
        private void InitializeLogger(IConnectionInfo cxinfo)
        {
            if (!EnableSqlLogging(cxinfo))
            {
                return;
            }

            if (_logger == null)
            {
                _logger = new SqlLogger();
            }
            _logger.Reset();
        }
Example #2
0
    private void InitializeLogger(IConnectionInfo cxinfo) {
      if (!EnableSqlLogging(cxinfo)) return;

      if (_logger == null) {
        _logger = new SqlLogger();
      }
      _logger.Reset();
    }