On Sat, Jan 15, 2011 at 00:47, Romy <[email protected]> wrote: > On Jan 10, 6:37 am, Gaetan de Menten <[email protected]> wrote: >> > Is elixir development active ? >> >> Active... Not really. I have several "almost implemented" features >> lying in my working copy at home, but given that I no longer use >> relational databases during my day work, I only work on Elixir once in >> a while (it competes with all my other hobbies). Honestly, unless >> someone picks up the maintainership, it will continue to slowly slide >> towards irrelevance. I'm sad to see all the effort I've put into it go >> to waste, but let's face it: it's unlikely I'll ever have time to >> "finish" the project (it has a quite narrow scope so finishing it >> would be possible for someone with more time to devote to it than me). > > I'm surprised nobody stepped in to work on it -- despite the extra > layer of abstraction, I would rather use Elixir than raw SQLAlchemy in > many cases. Makes me wonder what everyone else is using that's causing > it to, as you say, slide towards irrelevance ?
Nowadays most people use SQLAlchemy's built-in declarative module. >> On Sun, Jan 9, 2011 at 06:20, Romy <[email protected]> wrote: >> > Wondering because I've commented on a bug a few days ago w/out >> > response (http://elixir.ematia.de/trac/ticket/61) >> >> Well that particular patch wasn't merged because it can break some >> uses cases (it disallows having several entities with the same name in >> the same module), which can be valid in some cases, while the correct >> fix is elsewhere (as said in the bug report comments). And besides, >> this wouldn't happen if migrate didn't use reload (which breaks a lot >> of code). > > Migrate's a pain in the ass to use with Elixir. This is very > unfortunate. Could you be more specific? Have you read the simple workaround I proposed in that bug report? -- 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.
