Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>That's normal behavior, and cannot be changed : the newline after a closing <code>?&gt;</code> is always ignored.</p> <p><br> Here's the reference, in the FAQ of the PHP manual : <a href="http://fr.php.net/manual/en/faq.using.php#faq.using.newlines" rel="nofollow noreferrer">Hey, what happened to my newlines?</a> <br><em>(quoting, emphasis mine)</em></p> <pre><code>&lt;pre&gt; &lt;?php echo "This should be the first line."; ?&gt; &lt;?php echo "This should show up after the new line above."; ?&gt; &lt;/pre&gt; </code></pre> <blockquote> <p>In PHP, the ending for a block of code is either "<code>?&gt;</code>" or "<code>?&gt;\n</code>" (where <code>\n</code> means a newline). <br>So in the example above, the echoed sentences will be on one line, <strong>because PHP omits the newlines after the block ending</strong>. <br>This means that you need to insert an extra newline after each block of PHP code to make it print out one newline. <br><br>Why does PHP do this? <br>Because when formatting normal HTML, this usually makes your life easier because you don't want that newline, but you'd have to create extremely long lines or otherwise make the raw page source unreadable to achieve that effect.</p> </blockquote> <p><br> And here are a couple of interesting reads about this :</p> <ul> <li><a href="http://en.wikibooks.org/wiki/Complete_PHP_Programming/Escaping_from_HTML#Rules_pertaining_to_HTML_or_whitespace_preceding_or_following_PHP_tags" rel="nofollow noreferrer">Rules pertaining to HTML or whitespace preceding or following PHP tags</a></li> <li><a href="http://shiflett.org/blog/2005/oct/php-stripping-newlines" rel="nofollow noreferrer">PHP Stripping Newlines</a></li> <li><a href="http://brian.moonspot.net/php-history-newline-closing-tag" rel="nofollow noreferrer">The history of PHP eating newlines after the closing tag</a> <em>-- goes back to PHP 3 ^^</em></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POPHP omits a return
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPascal MARTIN
    1. USPascal MARTIN
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    1. COIn fact, nowerday it advised to not use the closing tag at all (on the end of the files)
      singulars
      1. PO
      1. USFrenck
    2. CONot quite true Frenck. It's advised not to use the closing tag in your application code. If you're using PHP as a template language it's impossible NOT to use the closing tag.
      singulars
      1. PO
      1. USAlan Storm
    3. COThat's correct Alan, kinda forgot to mention that...
      singulars
      1. PO
      1. USFrenck
 

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