> Hi all, > > I think the current description of Elixir (which is found at many > different places: index page of our website, pypi, README, ...) is > quite out of date and does not reflect the true nature and > specificities of Elixir anymore (especially since SQLAlchemy got its > own builtin "declarative" extension).
I hope you don't mind my response; I don't want to discourage you or anything. :( I, personally, kind of find the new description to be a little confusing. The original description seems to target people who know very little about using objects to represent a database. The new description seems to target people who already know a little bit about SQLAlchemy and want more details. Is this what you had in mind? I must admit that the original description seems to do a pretty good job of explaining Elixir to people who are completely new to the concept. Still, it could always use improvement, like you talked about. Ok, so maybe I should write something for you right? :) Well, I don't really know enough to do something like that, but maybe I can suggest something and see if you like it? Since I don't know enough about Elixir, here's my rather poor suggestion: Elixir is a layer on top of the SQLAlchemy library. It simplifies much of the boilerplate code from SQLAlchemy, resulting in code that is easier to work with and is cleaner to look at. Since Elixir is only a layer on top of SQLAlchemy, all of Elixir's core features come from SQLAlchemy. About SQLAlchemy: SQLAlchemy provides a way to map Python classes to the tables in a database. <See Example> Instead of invoking SQL commands to manipulate the database, you, instead, work with the Python objects. These objects automatically update themselves to the database. Thus, you can work with the database using only Python. Within this Python object atmosphere, SQLAlchemy supports several a range of database features, such as ManyToOne and ManyToMany relationships, versioning system for tables/rows, Pythonic querying of databases, and so on. Of course, you can probably word that last paragraph better. But anyways, even if you don't like my suggestion, my first question would be, did I describe Elixir accurately (since I'm not 100% sure I understand it all)? <See Example> = for the see example link, I thought it would be really helpful if people could visually see what this means. This could link to a page that shows two pictures: 1) a picture of a Elixir class like here: http://elixir.ematia.de/trac/wiki and 2) a picture of the SQL code that class get's translated into. That way, people who are new to the concept can see what this whole database tables as python objects really means. _________________________________________________________________ Bing brings you maps, menus, and reviews organized in one place. http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1 -- You received this message because you are subscribed to the Google Groups "SQLElixir" group. To post to this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlelixir?hl=en.
