문제

DISCLAIMER: I'm new to Grok.

I've been thinking about writing a business application (like accounting/sales/payroll) with Grok and ZODB.
As you know, a business application

  1. does a lot of INSERT.
  2. does a lot of SELECT on usually large sets of data.
  3. runs ad-hoc queries (a.k.a reports) on the data.

Now I was wondering if these requirements can be satisfied with ZODB. I'm sure (1) is a piece of cake but I have absolutely no idea about (2) and (3).

What do you folks, experienced with ZODB (and Grok), think about this? I'd really appreciate any hint/idea.

TIA,

도움이 되었습니까?

해결책

In this post (http://www.coactivate.org/projects/topp-engineering/blog/2009/03/20/to-zodb-or-not-to-zodb) the author presents two characteristics (disadvantages?) of ZODB:

  • No ad-hoc queries.
  • Migrations are inconvenient and expensive.

ZODB is very interesting but, IMHO, the major drawback is that the data is dependent of original code.

Grok is a good framework, but maybe you can look Pyramid (www.pylonsproject.org), that has also support for traversal and ZODB, with the advantage of a more numerous community.

라이센스 : CC-BY-SA ~와 함께 속성
제휴하지 않습니다 StackOverflow
scroll top