Home/ Questions/Q 6378821
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T02:03:28+00:00

So what I currently have is my tables in SQL, with table connecting different

  • 0

So what I currently have is my tables in SQL, with table connecting different table, e.g.

Table1: id, identifier, other_attributes
Table2: id, identifier, other_attributes
Table3: id, table1_id, table2_id // this connects table 1 and 2.

So I have made an object for table1 and table2, allowing things like $table = new table1($id); and $table->getName(); or $table->setName();

However, I’m not quite sure if this is the best way? And if it is, would it be best to create another object for table3? or is there better way to do this?

Finally, what I’ve done is combine getters and setters, meaning $table->name('somename'); will set the name, and $table->name(); will get it. Is it wise to combine them? or better to separate them?

Hosh

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I would use objects for each really used object (as the name states somehow…).

    For example I have a single user-class, which uses data from three different DB-tables. The n:m relation-tables should be implemented as their names indicate. Having a table ‘user_has_address’, I would implement the SQL-queries on the user-class too (which the uses an Address-class). But data from a table like ‘company_has_employees’ would reside in a company-class.

    And how to name your getters and setters in PHP is a matter of coding-convention (e.g. in your company or just your own). You don’t need them at all in PHP when using magic-methods (like __call()), but as noted by @JJ, it would make testing easier.

    • 0