A Module Is The Best Practice To Build Queries For Read Only Tables

My system has a second database that offers information about customers and sales (I cannot modify this data, only read from the database).

The database structure is huge and I do not need access for all tables, but I do need build some relationships between tables to retrieve the correct and appropriate information.

I was wondering, if a ‘Module’ is the best practice to do that?

Sure!

[size=2]Ok, So, let’s say my database structure is something like this:[/size]

USER

USER_CONTACT

USER_ADRRESS

In that case, would be better I create 3 models, each one related with one database table, right?!

BUT, I really don’t need do something specific on tables USER_CONTACT and USER_ADDRES. For sure I will create some queries to grab data from the 3 tables with JOIN.

So, in this case, it’s ok I create only one model ‘User’ and in this model link together with the other two tables?

No, you should use many models how many tables are used.

In your case you should use correctly 3 tables.