-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document database interceptors with examples #1543
Comments
ajcvickers
changed the title
Querying Data in a System-Versioned Temporal Table
Document database interceptors with examples
Sep 2, 2019
I am also waiting for this. |
ajcvickers
added a commit
that referenced
this issue
Oct 17, 2020
**No TOC yet since we need to decide what to do with `Fundamentals`. @smitpatel I do not intend to merge this way.** * Fixes #2615: Add information on controlling suppressing warnings and otherwise configuring EventIds * Fixes #2557: Support logging on DB level #2557 * Fixes #2770: Add entry in TOC for logging/interceptors * Fixes #583: Document how to use DiagnosticSource/DiagnosticListener * Fixes #673: Document EnableSensitiveDataLogging * Fixes #1913: Interception of database operations: InterceptionResult or InterceptionResult<DbDataReader>? * Fixes #1543: Document database interceptors with examples * Fixes #955: Document EnableRichDataErrorHandling * Fixes #661: EF Core 2.1: document state change events
ajcvickers
added a commit
that referenced
this issue
Oct 17, 2020
**No TOC yet since we need to decide what to do with `Fundamentals`. @smitpatel I do not intend to merge this way.** * Fixes #2615: Add information on controlling suppressing warnings and otherwise configuring EventIds * Fixes #2557: Support logging on DB level #2557 * Fixes #2770: Add entry in TOC for logging/interceptors * Fixes #583: Document how to use DiagnosticSource/DiagnosticListener * Fixes #673: Document EnableSensitiveDataLogging * Fixes #1913: Interception of database operations: InterceptionResult or InterceptionResult<DbDataReader>? * Fixes #1543: Document database interceptors with examples * Fixes #955: Document EnableRichDataErrorHandling * Fixes #661: EF Core 2.1: document state change events
ajcvickers
added a commit
that referenced
this issue
Oct 17, 2020
**No TOC yet since we need to decide what to do with `Fundamentals`. @smitpatel I do not intend to merge this way.** * Fixes #2615: Add information on controlling suppressing warnings and otherwise configuring EventIds * Fixes #2557: Support logging on DB level #2557 * Fixes #2770: Add entry in TOC for logging/interceptors * Fixes #583: Document how to use DiagnosticSource/DiagnosticListener * Fixes #673: Document EnableSensitiveDataLogging * Fixes #1913: Interception of database operations: InterceptionResult or InterceptionResult<DbDataReader>? * Fixes #1543: Document database interceptors with examples * Fixes #955: Document EnableRichDataErrorHandling * Fixes #661: EF Core 2.1: document state change events
ajcvickers
added a commit
that referenced
this issue
Oct 17, 2020
**No TOC yet since we need to decide what to do with `Fundamentals`. @smitpatel I do not intend to merge this way.** * Fixes #2615: Add information on controlling suppressing warnings and otherwise configuring EventIds * Fixes #2557: Support logging on DB level #2557 * Fixes #2770: Add entry in TOC for logging/interceptors * Fixes #583: Document how to use DiagnosticSource/DiagnosticListener * Fixes #673: Document EnableSensitiveDataLogging * Fixes #1913: Interception of database operations: InterceptionResult or InterceptionResult<DbDataReader>? * Fixes #1543: Document database interceptors with examples * Fixes #955: Document EnableRichDataErrorHandling * Fixes #661: EF Core 2.1: document state change events
ajcvickers
added a commit
that referenced
this issue
Nov 9, 2020
**No TOC yet since we need to decide what to do with `Fundamentals`. @smitpatel I do not intend to merge this way.** * Fixes #2615: Add information on controlling suppressing warnings and otherwise configuring EventIds * Fixes #2557: Support logging on DB level #2557 * Fixes #2770: Add entry in TOC for logging/interceptors * Fixes #583: Document how to use DiagnosticSource/DiagnosticListener * Fixes #673: Document EnableSensitiveDataLogging * Fixes #1913: Interception of database operations: InterceptionResult or InterceptionResult<DbDataReader>? * Fixes #1543: Document database interceptors with examples * Fixes #955: Document EnableRichDataErrorHandling * Fixes #661: EF Core 2.1: document state change events
ajcvickers
added a commit
that referenced
this issue
Nov 10, 2020
* Fixes #2615: Add information on controlling suppressing warnings and otherwise configuring EventIds * Fixes #2557: Support logging on DB level #2557 * Fixes #2770: Add entry in TOC for logging/interceptors * Fixes #583: Document how to use DiagnosticSource/DiagnosticListener * Fixes #673: Document EnableSensitiveDataLogging * Fixes #1913: Interception of database operations: InterceptionResult or InterceptionResult<DbDataReader>? * Fixes #1543: Document database interceptors with examples * Fixes #955: Document EnableRichDataErrorHandling * Fixes #661: EF Core 2.1: document state change events
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are implementing a solution to query a temporal of any table.
As you know, when enabling a temporal table on SQL server for any table, SQL will automatically add a second table with extra “_History” at the end of the table to track history. For example, if we have a “student” table, SQL server will add “student_History” table.
To query the student history, all that we need is querying student table and add “FOR SYSTEM_TIME AS OF '2015-09-01 T10:00:00.7230011';” at the end of the statement. So instead of write:
Select * from student
We will write: Select * from student FOR SYSTEM_TIME AS OF '2015-09-01 T10:00:00.7230011'
Is there any way to automatically append this statement at the end of the query?
It is like intercepting the query and applying query filter like a soft table, but now it is not filtered, it is just statement at the end of the statement.
The text was updated successfully, but these errors were encountered: