[eluser]Johan André[/eluser]
I usually end up with one model per databasetable.
Sometimes a model can interact with several tables.
Let's say I have a table that holds different stores:
Code:
id int(11) auto_inc PRIMARY_KEY
name varchar(255)
city_id int(11)
...and maybe a table that holds all my cities (referenced by the city_id-field in the stores-table:
Code:
id int(11) auto_inc PRIMARY_KEY
name varchar(255)
I would make the store-model use both the stores and cities-tables.
As jedd said, theres nothing right or wrong.
Try to group similar or connected functionality is my go.
Good luck!