Databases
StackOverflow2013
Postsdbo
POCreate view or use innerjoins?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCreate view or use innerjoins?
    primarykey
    data
    text
    <p>I have a normalized database, with foreign keys/primary keys giving one to many databases.</p> <p>I plan to access this database with PHP for the basic frontend/backend display. Now, my question comes from these two exampled queries: </p> <pre><code>CREATE VIEW `view` AS SELECT functiondetails.Detail, functionnames.ID, functionnames.FunctionName, functionnames.Catogory FROM functiondetails INNER JOIN functionnames ON functiondetails.AsscID = functionnames.ID </code></pre> <p>or</p> <pre><code>SELECT functiondetails.Detail, functionnames.ID, functionnames.FunctionName, functionnames.Catogory FROM functiondetails INNER JOIN functionnames ON functiondetails.AsscID = functionnames.ID </code></pre> <p>There is no error within the query as i've ran both without fail, but my overall question is this:</p> <p>if I plan to constantly reference alot of information from my database. Wouldn't it be easier to create a view, which will then update all the time with the newly added information, or would it be in better practice to have the second query on my actual php.. Example: </p> <pre><code>$Query = $MySQli-&gt;prepare(" SELECT functiondetails.Detail, functionnames.ID, functionnames.FunctionName, functionnames.Catogory FROM functiondetails INNER JOIN functionnames ON functiondetails.AsscID = functionnames.ID ") $Query-&gt;execute(); $Results = $Query-&gt;fetch_results(); $Array = $Results-&gt;fetch_array(MYSQLI_ASSOC); </code></pre> <p>Or to select from my view? </p> <pre><code>$Query = $MySQLi-&gt;prepare("SELECT * FROM `view`"); $Query-&gt;execute(); $Results = $Query-&gt;fetch_results(); $Array = $Results-&gt;fetch_array(MYSQLI_ASSOC); </code></pre> <p>So which one would be a better method to use for querying my database? </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAlexander Yancharuk
    1. USDaryl Gill
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCreate view or use innerjoins?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCreate view or use innerjoins?
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    3. VO
      singulars
      1. POCreate view or use innerjoins?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI 'think' both options are essentially the same. The advantage of the view (as I see it) is that you can grant a user access to it without granting them access to your core tables.
      singulars
      1. POCreate view or use innerjoins?
      1. USStrawberry
    2. CORelated info on http://dba.stackexchange.com/questions/16372/when-to-use-views-in-mysql and http://stackoverflow.com/questions/10302615/mysql-views-performance. Hope this helps.
      singulars
      1. POCreate view or use innerjoins?
      1. USAnda Iancu
    3. COI am always using views for simplifying my code and queries :)
      singulars
      1. POCreate view or use innerjoins?
      1. This table or related slice is empty.
 

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