Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It really depends on what you need.</p> <p>For example if the page has big part that change completely, what I would suggest is to create different templates and include them depending on their "permissions"</p> <pre><code> $permission = $_SESSION['type_user']; include '/path/to/file/with/permission/'.$permission.'/tpl.html'; </code></pre> <p>and have something in the page similar to</p> <pre><code>&lt;?php //inside include.php you have the line similar to //$permission = isset($_SESSION['type_user']) &amp;&amp; $_SESSION['type_user']!=''?$_SESSION['type_user']:'common'; require_once '/mast/config/include.php'; include '/path/to/file/with/permission/common/header.html'; include '/path/to/file/with/permission/'.$permission.'/tpl_1.html'; include '/path/to/file/with/permission/common/tpl_2.html'; include '/path/to/file/with/permission/'.$permission.'/tpl_3.html'; include '/path/to/file/with/permission/common/footer.html'; ?&gt; </code></pre> <p>if the script is full of small parts like "show this text", or "show this button", you can create a function that will check the permissions for you</p> <pre><code>&lt;?php function can_user($action, $what){ switch($action){ case 'write': return $your_current_if_on_what; break; case 'read': default: return $your_current_if_on_what; break; } } ?&gt; and the template will look like: [my html] &lt;?=can_user('read','button')?'My Button':''?&gt; [my html] </code></pre> <p>As a rule of thumb, if a piece of code is used more than 2 times, it needs to be put in a function/file separately, so if you have many "IFS" you need to create a function</p>
    singulars
    1. This table or related slice is empty.
    1. PODisplaying same page differently for users with different roles
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USFabrizio
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODisplaying same page differently for users with different roles
      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. Though took me some time to understand, i got it. Any idea how is this done by big professional websites?
      singulars
      1. PO
      1. USParas Narang
    2. CODepend what you mean with big professional sites. I run and developed for big sites, and each time is a different solution depending on what the parameters are. For example you have to keep in mind that each time that PHP has to access the file system it has a big performance problem, but some accelerator/optimizers often can help (I use eAccelerator).
      singulars
      1. PO
      1. USFabrizio
    3. COMy last 2 big sites I used a combination of the two where the template that I wanted to include was passed to the "can_user", and the returned the template name itself or a different template name when they user didn't have the permission to see that part. something like `include can_user('read','button','button_html');` and the can_user function will be `return $this_user_can?$template,'permission_deny_in_page';`
      singulars
      1. PO
      1. USFabrizio
 

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