Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It absolutely is. Given the relational nature of MySQL and other relational databases, it is very easy to define your PHP objects and code representations of the mysql tables. Consider this overly simple class:</p> <pre><code>&lt;?php class Note { private $id private $text; private $insert_dt; private $update_dt; } ?&gt; </code></pre> <p>What this allows you to do is better organize and reuse functionality without the need for code duplication or hunting around your codebase. For instance, say I want to start printing out the insert date for every note a particular way across all pages. How would I do this? I could potentially have to change every page on the site.</p> <p>If we have properly defined setters and getters, this becomes an exceedingly simply task. I should only have to replace the formatted return string in 1 (very obvious) location:</p> <pre><code>&lt;?php class Note { // ... public function getFormattedInsertDate() { return date( "M, Y", $this-&gt;insert_dt ); } } ?&gt; </code></pre> <p>Admittedly, this all seems very excessive and time consuming on a small scale. I remember building a personal site for myself in college when I had extensive OO experience. I was learning PHP at the time and for the site I tended to use inline code simply for the speed. It worked fine, was very fast and lightweight. I didn't understand the hullabaloo over web frameworks, as they felt overly "heavy".</p> <p>The issues arise after the fact during maintenance. When you return to code 6 months or years later, you try and figure out where this call was, or why you have to change it in 8 places to fix a bug. These are the feelings caused by bad coupling - cohesion in your codebase.</p> <p>Luckily, many frameworks have sprung up over the years to not only support but encourage and enforce this behavior. If you haven't I would strongly suggest looking into CakePHP or Code Igniter. They are both pretty easy to leaner frameworks that really nail down these concepts well, as well as provide excellent introductory tutorials to walk you through creating a blog website.</p> <p>I hope this helps. Let me know if I missed anything and I'll update this as needed.</p>
    singulars
    1. This table or related slice is empty.
    1. POPHP OOP vs Inline
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBen Roux
    1. USBen Roux
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPHP OOP vs Inline
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for the help Ben! So in my example you would move everything to one class? Would you roll up the javascript and everything into one class and then call like echo $newnote->show_notes(); on your main page? Geez, I feel like I'm close to understanding when to use classes but just can't quite get there for some reason.
      singulars
      1. PO
      1. USDev Newb
    2. COThe real goal is to make your way to Model-View-Controller, but again, to simplify, I would say if you are pulling from a database, that table should have a class. Keep your client languages (html, css, js) in their own files. When you need data, as you suggested, simply reference the class.
      singulars
      1. PO
      1. USBen Roux
    3. COOkay, that helps alot. Thanks! I wish I would have started with a framework but I didn't anticipate my first project being so big. Now that I am knee deep I need to find ways to move in the right direction. The advice helps.
      singulars
      1. PO
      1. USDev Newb
 

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