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
* Drop support for Elixir 1.3.x, as was done in corresponding Ecto master branch during that time.
* Update deps to match Ecto 2.2 branch.
* Drop support for OTP 18.0. Continue to test against OTP 18.2 as does Ecto 2.2.x release.
* Sadly, we now have to punt on Decimal support. There's really no way to store precision accurately.
* Prepare version 2.2.0 release.
* Add note about Ecto 2.x version compatibility.
This version only works with Ecto 2.2.x. I tried it with the latest 2.1.x release and it was broken (relying on APIs that don't exist in that series).
Copy file name to clipboardExpand all lines: README.md
+9-3
Original file line number
Diff line number
Diff line change
@@ -5,17 +5,23 @@
5
5
6
6
# sqlite_ecto2
7
7
8
-
`sqlite_ecto2` is an Ecto 2.x adapter that allows you to create and maintain SQLite3 databases.
8
+
`sqlite_ecto2` is an Ecto 2.2.x adapter that allows you to create and maintain SQLite3 databases.
9
9
10
10
Read [the tutorial](./docs/tutorial.md) for a detailed example of how to setup and use a SQLite repo with Ecto, or just check-out the CliffsNotes in the sections below if you want to get started quickly.
11
11
12
12
13
+
## Ecto Version Compatibility
14
+
15
+
**IMPORTANT:** This release will _only_ work with Ecto 2.2.x. If you need compatibility with older versions of Ecto, please see:
If, for some reason, you still need to use Ecto 1.x, please look at [sqlite_ecto](https://github.com/jazzyb/sqlite_ecto), on which this project is based.
18
-
19
25
I strongly recommend reading [Appropriate Uses for SQLite](https://sqlite.org/whentouse.html) on the SQLite site itself. All of the considerations mentioned there apply to this library as well.
20
26
21
27
I will add one more: If there is *any* potential that more than one server node will need to write directly to the database at once (as often happens when using Elixir in a clustered environment), **do not use**`sqlite_ecto2`. Remember that there is no separate database process in this configuration, so each of your cluster nodes would be writing to its **own** copy of the database without any synchronization. You probably don't want that. Look for a true client/server database (Postgres, MySQL, or similar) in that case. SQLite's sweet spot is single-machine deployments (embedded, desktop, etc.).
0 commit comments