| 3 | | ----- |
| 4 | | |
| 5 | | TODO |
| | 3 | ===== |
| | 4 | |
| | 5 | ------- |
| | 6 | History |
| | 7 | ------- |
| | 8 | |
| | 9 | In 2006, `Jonathan LaCour <http://cleverdevil.org>`_ discovered the fantastic |
| | 10 | `SQLAlchemy <http://sqlalchemy.org>`_ project, and really liked its power and |
| | 11 | flexibility, but found that in many simple cases he would prefer a simpler and |
| | 12 | more attractive way to declare his model objects. As a result, Jonathan spent |
| | 13 | a few hours on a weekend to create the `ActiveMapper |
| | 14 | <http://cleverdevil.org/computing/35/>`_ SQLAlchemy extension. For a weekend's |
| | 15 | worth of work, it wasn't half bad, and gained a little bit of traction in the |
| | 16 | wild. But, over time, it became clear that ActiveMapper needed a lot of work |
| | 17 | to stabilize and become more useful. |
| | 18 | |
| | 19 | Later that year, `Daniel Haus <http://www.ematia.de>` released his own layer |
| | 20 | on top of SQLAlchemy, called `TurboEntity <http://turboentity.ematia.de>`_. |
| | 21 | TurboEntity solved some of the problems of ActiveMapper, and took a slightly |
| | 22 | different approach to the problem. TurboEntity also began to gain some ground |
| | 23 | and it became clear to both Daniel and Jonathan that they needed to work |
| | 24 | together. |
| | 25 | |
| | 26 | Around the same time, Gaëtan de Menten contacted both Jonathan and Daniel to |
| | 27 | reveal that he had been working on his own layer as well. A few weeks later, |
| | 28 | all three agreed to work together to create a replacement for TurboEntity and |
| | 29 | ActiveMapper using their collective experience and knowledge. |
| | 30 | |
| | 31 | |
| | 32 | -------- |
| | 33 | The Name |
| | 34 | -------- |
| | 35 | |
| | 36 | The Oxford English Dictionary defines Elixir as: "a magical or medicinal potion, |
| | 37 | a preparation that was supposedly able to change metals into gold, sought by |
| | 38 | alchemists." |
| | 39 | |
| | 40 | |
| | 41 | ---------- |
| | 42 | The Future |
| | 43 | ---------- |
| | 44 | |
| | 45 | The eventual goal of the Elixir project is to become an official SQLAlchemy |
| | 46 | extension. But, before we submit elixir for inclusion within SQLAlchemy, we |
| | 47 | want the opportunity to solicit feedback and contributions from users to make |
| | 48 | sure that we have ironed out any bugs, missing features, syntax changes, or |
| | 49 | documentation deficiencies. |
| | 50 | |
| | 51 | The primary things we would like to resolve before we make our first stable |
| | 52 | and official release are: |
| | 53 | |
| | 54 | - TODO |