I am questioning the decision to make bean.module use the core block table. There are some modules that try to load blocks and may not be aware that there's another module that can produce a lot (LOT!) of blocks.

Code that may be acceptable for loading a few dozen blocks suddenly tries to load a couple of thousands...

That's not really good.

Contrib modules shouldn't abuse core tables, there sure must be another way.

Comments

Leeteq’s picture

Leeteq commented
Category: Bug report » Task
Priority: Normal » Major
indytechcook’s picture

indytechcook commented
Status: Active » Closed (works as designed)

bean does not use the bug table but exposes blocks via hook_block_info. This was done to make the integration to blocks as seamless as possible. Which adds integration to modules like context and panels.

If someone has a couple thousands instances of beans, then they are either on a really huge, complex site or mis-using the modules.

At this point, there won't be any major architecture decisions to the bean module.