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
Logging of executed SQL is available, which is good, but it would be nice to also have transaction operations in the log. It would be a great addition when analyzing what's happening. SQL logging should probably (optionally?) include transaction identifier in that case.
The text was updated successfully, but these errors were encountered:
Best would be to be able to specify from client code - some apps may even need to be able to specify it differently for different SQL commands even in the same transaction.
If that's too much hassle, then I'd suggest debug. I wouldn't think that it would be a very common situation to want SQL to be logged in production where no debugging is in progress.
Logging of executed SQL is available, which is good, but it would be nice to also have transaction operations in the log. It would be a great addition when analyzing what's happening. SQL logging should probably (optionally?) include transaction identifier in that case.
The text was updated successfully, but these errors were encountered: