ZF2, I need advice about structure

[dam358]

Hello,
I'm quite new in ZF2 (1 month) and i'm working on it.

I've got a question about the application that i'm developping.
This application will grow, offer multiple services to a lot of users and ask a lot of tables in database.

So, in the construction of my application, do you think it's better to use the vision of 1table/1model (as in tutorial with the Album) or use some "shortcuts".
For example, to get data in my structure, instead of calling 20 models calling 20 tables and then store datas, do a "big request" and directly store datas in my structure ?

I think this 2nd way will be easier and faster to do but harder to evolve in the future.

Could you help me ? I need opinions.

Thanks.

[chantrelle]

Why is no-one from Zend answering these questions? HELLO ZEND?

[frandy]

Hey,

I'm not someone from Zend, but I may can give you an advise.
As far as we learned it in our application design courses, for each table one model. You can go further be creating a model for more complex sql views. Better would be to use service classes, that would group tasks involving multiple models which would depend on how the tables are related.

Best regards