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
This change adds support for SQLite3 storage of errors and includes a new `error_tracker_meta` table to store metadata needed for ErrorTracker to function properly - like managing migration versions.
Aside from adding support to SQLite3, which was as easy as expected, we have also added a way to track migration versions that should work in any SQL database (although only PostgreSQL and SQLite3 are currently supported). That KV store table will also work in the future to store runtime configuration, for example.
In this change we are also migrating PostgreSQL systems to use this new table, which means migrating from using table comments to store migration version to use this new table.
As for SQLite3 migrations, migrations start at `V02` to maintain the same version IDs on all platforms.
Copy file name to clipboardExpand all lines: guides/Getting Started.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ This guide is an introduction to ErrorTracker, an Elixir-based built-in error tr
4
4
5
5
In this guide we will learn how to install ErrorTracker in an Elixir project so you can start reporting errors as soon as possible. We will also cover more advanced topics such as how to report custom errors and how to add extra context to reported errors.
6
6
7
-
**This guide requires you to have set up Ecto with PostgreSQL beforehand.**
7
+
**This guide requires you to have set up Ecto with PostgreSQL or SQLite3 beforehand.**
0 commit comments