Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A function should have clearly defined, narrow responsibilities with clearly defined, minimalist return types. If you start to create "god functions" which do everything and the kitchen sink depending on what arguments you pass, you're going heavily into the territory of hard to maintain spaghetti code. You do not want a function that does A and returns B if you pass it X, but does C and returns D if you pass it Y etc...</p> <p>It is a good idea to start <em>concrete</em> and generalize over time as you see similar patterns emerge. So, create the methods you actually need:</p> <pre><code>public function findUserById($id) public function findUserByEmail($email) public function updateCompanyName($id, $newName) </code></pre> <p>If you find you have shared code between these functions, unify the code behind the scenes to keep it DRY:</p> <pre><code>public function findUserById($id) { return $this-&gt;find('SELECT * FROM user WHERE id = ?', $id); } public function findUserByEmail($email) { return $this-&gt;find('SELECT * FROM user WHERE email = ?', $email); } protected function find($query, $arg) { ... } </code></pre> <p>Don't start the other way around, thinking you "only need X,Y and Z" which seem similar enough to be unified into one method, then later finding out there are small differences between X, Y and Z and littering your code with special cases for each. That just leads to functions which are either ginormous or so general they basically do nothing on their own.</p>
    singulars
    1. This table or related slice is empty.
    1. POmultiple functions is one big function in PHP?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdeceze
    1. USdeceze
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POmultiple functions is one big function in PHP?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI think, you are right. Nevertheless, I whould suggest another solution for this. In my opinion, `findUserById` should not return an array, but an popo-object (just my flavor). `findUserByEmail` should return the `id`, because `findUserById` should be the only responsible function to return the "user". `find` should return only a simple array which contains the ids. `updateCompanyName`? Again, too much responabilities. You have to call the implicit `save`-method again and again. As I said below, this topic is fairly big...
      singulars
      1. PO
      1. USRon
    2. CO@Ron Sure, these are just very general examples. I'm not advocating exactly this code, just illustrating the way of thinking.
      singulars
      1. PO
      1. USdeceze
    3. COThat's the answer I was looking for. I feared that making "god-like" functions would create long term problems of of later maintaining. I guess you are right and making functions do specific things is the way to go. Thanks for very detailed and easy-to-understand answer ;)
      singulars
      1. PO
      1. USSandro Dolidze
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload