for me it depends on where the data is mostly used.

But to me, it sounds like you would want to have your schema at the package level, and then lean on a model.

Block level tables are a quick and dirty way to bypass the need for a model if you are strictly working in a block context as C5 has all the data save and update methods built into the block model. But it's all local to the the block. You "can" access that data in any event, but you'll end up needing your own model anyway.

Chad

personally i don't thing it really matters, i would think keep the tables that the blocks require in the blocks,

and the shared tables in the top level db.xml

Thanks guys, sounds like the package level is the best way to go although I'll keep a couple of the tables which are specific to each block at the block level.

I'd create the tables in db.xml in package root, the rest of them would be block specific views of data(db fields for templates, and the block's db.xml would store view specific data.

If you want to write to db tables from the block's save, you need to specify a save method in your block controller then call parent::save();, which calls the inherited classes save method which handles bID and things like that(and extracting db values from the post array($args);