Release v0.10.1

elixir-ecto · Mar 25, 2015 · 930f218 · 930f218
1 parent 49b7ee6
commit 930f218
Show file tree

Hide file tree

Showing 3 changed files with 15 additions and 3 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,9 +1,13 @@
 # Changelog
 
-## v0.10.1-dev
+## v0.10.1 (2015-03-25)
+
+* Enhancements
+  * Add an option to set the engine when creating a table (used by MySQL and defaults to InnoDB). This ensures Ecto works out of the box with earlier MySQL versions
 
 * Bug fixes
   * No longer create database in `ecto.migrate` if one does not exist
+  * Fix a bug where dates earlier than 2000 could not be saved in Postgres
 
 ## v0.10.0 (2015-03-21)
 

diff --git a/lib/ecto/adapters/mysql.ex b/lib/ecto/adapters/mysql.ex
@@ -46,6 +46,15 @@ defmodule Ecto.Adapters.MySQL do
   There are some limitations when using Ecto with MySQL that one
   needs to be aware of.
 
+  ### Engine
+
+  Since Ecto uses transactions, MySQL users running old versions
+  (5.1 and before) must ensure their tables use the InnoDB engine
+  as the default (MyISAM) does not support transactions.
+
+  Tables created by Ecto are guaranteed to use InnoDB, regardless
+  of the MySQL version.
+
   ### UUIDs
 
   MySQL does not support UUID types. Ecto emulates them by using

diff --git a/mix.exs b/mix.exs
@@ -1,8 +1,7 @@
 defmodule Ecto.Mixfile do
   use Mix.Project
 
-  @version "0.10.0"
-  @adapters [:pg]
+  @version "0.10.1"
   @adapters [:pg, :mysql]
 
   def project do