Show HN: Statetrace – Annotated Audit Trail for Postgres and MySQL
1–6 of 6 posts
Re: Show HN: Statetrace – Annotated Audit Trail for Postgres and MySQL
#2how does the timetravel feature work?
Re: Show HN: Statetrace – Annotated Audit Trail for Postgres and MySQL
#3how does the timetravel feature work?
Time Travel works by generating a SQL statement or a CTE, which transforms the raw audit events into a snapshot of the table at a point in time with extra columns for the annotations. This feature is currently exposed on the enterprise product through the UI (which exposes a SQL explorer for your warehouse), but we are slowly shifting those features into the GQL API of core (give a table name, get a SQL model). Time travel works on the transaction level so you don’t lose any fidelity.
Re: Show HN: Statetrace – Annotated Audit Trail for Postgres and MySQL
#4Does it work with Wordpress / Drupal ?
Re: Show HN: Statetrace – Annotated Audit Trail for Postgres and MySQL
#5Does it work with Wordpress / Drupal ?
Short answer yes! Long answer: Statetrace works at two different levels. The first is to record the raw changes without annotations. Statetrace works 100% with any framework at this level.
The next level is to record with annotations. Currently we don’t have the annotation support for wordpress/drupal but it is something very easy to add.
Re: Show HN: Statetrace – Annotated Audit Trail for Postgres and MySQL
#6Does it work with Wordpress / Drupal ?
Short answer yes! Long answer: Statetrace works at two different levels. The first is to record the raw changes without annotations. Statetrace works 100% with any framework at this level. The next level is to record with annotations. Currently we don’t have the annotation support for wordpress/drupal but it is something very easy to add.
Thank you