# ArangoX Ecto


## Table of Contents

* [About the Project](#about-the-project)
  * [Built With](#built-with)
* [Getting Started](#getting-started)
  * [Prerequisites](#prerequisites)
  * [Installation](#installation)
* [Usage](#usage)
* [Roadmap](#roadmap)
* [Contributing](#contributing)
* [License](#license)
* [Contact](#contact)
* [Acknowledgements](#acknowledgements)

## About The Project

After playing around with different packages that implemented ArangoDB in Elixir, I found that there wasn't a package
that suited my needs. I needed ArangoDB to work with Ecto seamlessly but there was no up-to-date adapter for Ecto available.
ArangoX Ecto uses the power of ArangoX to communicate with ArangoDB and Ecto for the API in Elixir. Ecto is integrated
with many other packages and can now be used with ArangoDB thanks to this package.

### Built With

* [Arangox](

## Getting Started

To get the adapter integrated with your project, follow these simple steps.

### Prerequisites

* Elixir 1.10+ / Erlang OTP 23+

### Installation

Add the following line to your mix dependencies to get started.

{:arangox_ecto, "~> 0.6"}

## Usage

To connect to the database you need to specify the config values like so:

config :my_app, MyApp.Repo,
  database: "my_db",
  endpoints: ""

Only `database` and `endpoints` are required but there are other available options can be found in the [Arangox docs](

The database should be setup using
$ mix ecto.setup.arango

### Basic Usage

#### Repo Setup

To use the adapter in your repo, make sure your repo uses the `ArangoXEcto.Adapter` module for the adapter.

defmodule MyApp.Repo do
  use Ecto.Repo,
    otp_app: :my_app,
    adapter: ArangoXEcto.Adapter

#### Schema Setup

Since ArangoDB uses a slightly different id system, your schema must use the `ArangoXEcto.Schema` instead of

defmodule MyApp.Accounts.User do
    use ArangoXEcto.Schema
    import Ecto.Changeset

    schema "users" do
      field :first_name, :string
      field :last_name, :string


    @doc false
    def changeset(app, attrs) do
      |> cast(attrs, [:first_name, :last_name])
      |> validate_required([:first_name, :last_name])

#### Migration Setup

The adapter will automatically create collections if they don't already exist but there are cases where you might need
to use migrations. For example, if you needed to create indexes as well, the following would be used.

defmodule MyApp.Repo.Migrations.CreateUsers do
    use ArangoXEcto.Migration

    def up do

      create(index("users", [:email]))

    def down do

Using migrations should be avoided unless necessary.

### Raw AQL queries

A lot of the time it is far more efficient to just run a raw AQL query, there's a function for that.

    "FOR var in users FILTER var.first_name == @fname AND var.last_name == @lname RETURN var",
    fname: "John",
    lname: "Smith"

This query will return a result such as:

          "_id" => "users/12345",
          "_key" => "12345",
          "_rev" => "_bHZ8PAK---",
          "first_name" => "John",
          "last_name" => "Smith"

This is awesome functionality, but a lot of the time we will want to resemble a specific struct. This is actually quite
easy with the help of the `ArangoXEcto.raw_to_struct/2` function. The same query above could be extended to also convert
the output:

    "FOR var in users FILTER var.first_name == @fname AND var.last_name == @lname RETURN var",
    fname: "John",
    lname: "Smith"
  |> case do
      {:ok, results} ->
        |> ArangoXEcto.raw_to_struct(User)

      {:error, _reason} -> []

This will return something like:

      id: "12345",
      first_name: "John",
      last_name: "Smith"

This is clearly a much better representation of the result and can be used in further Ecto methods.

### Graph Relations

After a lot of tinkering, the best solution to graph relations in with Arango and Ecto was to not use Ecto a lot.

The adapter will dynamically create and manage edge collections. Each edge collection will be created as an Ecto
schema when they are first used. This will allow for more extensibility through ecto onto the edges. The module will
be created under the closest common parent module of the passed modules plus the `Edges` alias. For example, if the
modules were `MyApp.Apple.User` and `MyApp.Apple.Banana.Post` then the edge would be created at
`MyApp.Apple.Edges.UsersPosts`. This assumes that the edge collection name was generated and not explicitly defined,
if it was `UsersPosts` would be replaced with the camel case of that collection name.

To read more about Edge Schemas and how to extend edge schemas to add additional fields, read the docs on

To create and delete edges (as well as other useful methods) check out the
[full documentation](

In order to delete a specific edge, you can do it exactly as you would any other ecto struct
(since after all it is one).

Querying of edges can be done either through using an AQL query or by using Ecto methods.

### Further Usage

For more examples and full documentation, please refer to the [Documentation](

## Roadmap

See the [open issues]( for a list of proposed features (and known issues).

##### Some planned ideas:
* Named Graph integrations
* Easier Graph level functions
* Multi-tenancy

## Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are **greatly appreciated**.

1. Fork the Project
2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`)
3. Write some awesome code
4. Commit your Changes (`git commit -m 'Add some AmazingFeature'`)
5. Push to the Branch (`git push origin feature/AmazingFeature`)
6. Open a Pull Request

## License

Distributed under the Apache 2.0 License. See `LICENSE` for more information.

## Contact

Tom Grozev - [@tomgrozev]( -

Project Link: [](

## Acknowledgements

* [mpoeter]( - Wrote the original Ecto Query to AQL code