Thanks for the links, this is the first time I see this blog post indeed. I support the vision of Elixir you describe in there, and I still see value in this line of thinking.
I know those hooks became only recently available, it was a blog post from Michael Bayer that showed me how to use them for starting the setup process. On Wed, Sep 12, 2012 at 10:39 AM, Gaëtan de Menten <[email protected]> wrote: >> On Fri, Sep 7, 2012 at 1:13 PM, chaouche yacine <[email protected]> >> wrote: > >> However, I'm curious to know if there's a document explaining the >> architecture of this gem ? the 'how it works part' rather than the API or >> 'how to use' part. > > > On Tue, Sep 11, 2012 at 10:47 PM, Erik Janssens > <[email protected]> wrote: >> >> unfortunately not, such a document would be welcome :) >> >> we cannot copy it from the original Elixir implementation, since >> that one lacked such a document as well. only by reading the >> code, I discovered that one can do really nice things with >> Elixir that I was not aware of. > > > For what it's worth, back in the day, I wrote a blog post describing the > "vision" I had for Elixir. It can be found at: > http://ged.bugfactory.org/2009/01/elixirs-vision/ > > And on Elixir's wiki I started writing a page to explain how stuff work. I > never finished it but it should be an interesting read anyway. You can find > it at: > http://elixir.ematia.de/trac/wiki/BehindTheScene > > Maybe those two pages were not advertised enough. > >> where statements are the : using_options(...) stuff, the only >> reason I took those over was to be backward compatible, >> since all the stuff you can do with statements can be done >> with pure Declarative as well. >> >> but the relationship configuration is more complex, as here >> Elixir does preprocessing before moving things to Declarative, >> to connect inverse relations and generate foreign keys, >> relationship tables etc. >> >> This preprocessing step is interesting, as it can be used >> to 'automate' certain patterns that are used in applications, >> such as 'state', 'type' or things like that. > > > That has always been the goal of Elixir (at least for me). > >> The new implementation no longer needs the 'setup_all' call, >> and the confusing '__metadata__' > > > Great! (but to my defense, the hooks you use in SQLAlchemy that make this > possible didn't exist yet when I was still actively developing Elixir) > > -- > Gaëtan de Menten > > > > -- > You received this message because you are subscribed to the Google Groups > "SQLElixir" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sqlelixir?hl=en. -- You received this message because you are subscribed to the Google Groups "SQLElixir" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlelixir?hl=en.
