openerp-expert-framework team mailing list archive

[Leonardo Santagada <santagada@xxxxxxxxxxxx>]

2011/9/9 Raphael Valyi <rvalyi@xxxxxxxxx>

> Hello guys, some feedback:
>
> 1) Don't you have like an API de facto standard in Python? Django, other?
> Cause in OOOR we are implementing the Rails ActiveResource (inspired from
> ActiveRecord) API http://goo.gl/HyBKd (with some things from ActiveRecord
> that OpenERP API would support like relations or pagination). So it means
> that any Rails noob having a read some introduction to Rails is able to code
> using OOOR. I strongly advise you copy some existing standard instead of
> trying to re-invent the wheel, cause we always see where re-inventing the
> wheel leads; to temporary crap that should all be re-designed one day.
>

Looking at the python apis is a good idea, lets see the major contenders:

https://docs.djangoproject.com/en/dev/topics/db/queries/

Django is somewhat like ActiveRecord with the __lt and stuff like this.

http://www.sqlalchemy.org/docs/orm/query.html

sqlalchemy seems better, altough a little more verbose. What would be cool
about using the sqlalchemy api is that when we finally merge the sqlalchemy
branch we can only delete some code and everything would be fine.

Zope/Plone use an object database, which is great for them, but it doesn't
make any sense to use it on OpenERP.