Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'd create separate (protected) functions, those return a prepared statement that only needs to be executed.</p> <pre><code>/** * @returns PDOStatement */ protected function prepareStatementForCase1(PDO $dbObject,Object $dataToBind){...} /** * @returns PDOStatement */ protected function prepareStatementForCase2(PDO $dbObject,Object $dataToBind){...} </code></pre> <p>Then, I would decide outside, which one has to be called. You can rebuild, maintain and read the code more easily.</p> <p>Example:</p> <pre><code>class Document{ protected $dbObject; public function __construct(PDO $dbObject){ $this-&gt;dbObject=$dbObject; } public function doQuery($paramOne,$paramTwo,...){ $logicalFormulaOne=...; // logical expression here with parameters $logicalFormulaTwo=...; // logical expression here with parameters if($logicalForumlaOne){ $dbStatement=$this-&gt;prepareStatementForCase1($dataToBind); }else if($logicalFormuleTwo){ $dbStatement=$this-&gt;prepareStatementForCase2($dataToBind); } $dbResult=$dbStatement-&gt;execute(); } protected function prepareStatementForCase1(Object $dataToBind){ $dbStatement=$this-&gt;dbObject-&gt;prepare("query string"); $dbStatement-&gt;bindParam(...); return $dbStatement; } } </code></pre> <p>But I would not advice this, when your PDOResult object represents different type of database tuples, or when you return more rows in one of the cases.</p> <p>What I usually do is that I create a class which represents (in your example) a Document. Only one. I can insert, delete, select, modify by its fields, and handle one item. When I need to (for example) fetch more of them, I create a new class, e.g. DocumentList, which handles a collection of documents. This class would give me an array of Document objects when it fetches more of them.</p>
    singulars
    1. This table or related slice is empty.
    1. POWorking with dynamic prepared statements in PDO
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDyin
    1. USDyin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWorking with dynamic prepared statements in PDO
      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. VTAcceptedByOriginator
    1. CODyin, this sounds similar to what dqhendricks said. Would you be able to provide an example?
      singulars
      1. PO
      1. USPaul S.
    2. COI've improved my answer. You should make separate classes for those queries.
      singulars
      1. PO
      1. USDyin
 

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