Ensure that primary key value is valid when using Custom primary keys in Ecto.Repo.Backend.insert/4
Don't call Ecto.Model.put_primary_key/2 unless pk_field is valid
Integration Test for explicitly assigned non-default primary keys using Postgres adapter
Merge pull request #220 from TanYewWei/20140512-custom-primary-key

Ensure that primary key value is valid when using Custom primary keys in Ecto.Repo.Backend.insert/4
Update version in readme
Update postgrex dependnecy too
Convert associations to structs and proxies
Merge pull request #221 from elixir-lang/association-proxy

Convert associations to structs and proxies
Remove deprecated Mix.project/0
Update README to reference wiki entry on using Custom Primary Keys on Models
Update Ecto.Model.Schema docs
Fix for ecto.migrate task

Was throwing an error when executed. Talking to @josevalim on the google group and it turned out the fix is simply changing the "if" at line 45 to an "unless". Changing it resolved the error.
Merge pull request #228 from bryanjos/patch-1

Fix for ecto.migrate task
Fix migration task test
Merge branch 'master' into put-primary-key-readme
Update Ecto.Model.Schema moduledoc with notes on setting primary keys
Merge pull request #227 from TanYewWei/put-primary-key-readme

Update README to reference wiki entry on using Custom Primary Keys on Models
Add Ecto.Repo.one which returns either zero or one result.

If there are two or more results one raises Ecto.NotSingleResult.

Also Add Ecto.Repo.one!, change Ecto.Repo.get to have no limit and add
Ecto.Repo.get!
Merge pull request #210 from MSch/repo-one

Add Ecto.Repo.one which returns either zero or one result.
Use new exceptions