Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't think this looks right, because I don't think you <a href="http://www.codinghorror.com/blog/2008/05/openid-does-the-world-really-need-yet-another-username-and-password.html" rel="nofollow noreferrer">should ever store passwords in your database</a>. Especially when you ask such questions on Stackoverflow(I don't even recommend myself to store passwords inside my database, although I did a lot of research on this topic, but I still don't consider myself a security expert). I always recommend people to use OpenID(or Facebook Connect) instead. It is very simple to implement, secure. Most users already have an OpenID like for example Google openID or Yahoo! openID. I have a demo available at my hosting provider(simple) at location <a href="http://westerveld.name/php-openid/" rel="nofollow noreferrer">http://westerveld.name/php-openid/</a>. When you implement OpenID you don't need to worry about authentication at all. I have this code available at github. You could just simply clone code and get started => <a href="https://github.com/alfredwesterveld/php-openid" rel="nofollow noreferrer">https://github.com/alfredwesterveld/php-openid</a></p> <p>But If you really want to store passwords yourself I would advice you to look into <a href="http://www.openwall.com/phpass/" rel="nofollow noreferrer">phpass</a>. It supports the most secure hashing method OpenBSD-style Blowfish-based bcrypt <a href="https://stackoverflow.com/questions/4443476/optimal-bcrypt-work-factor">which is Moore's law proof</a>. I made a simple library wrapping phpass also available at github, although I don't advice you to use this => <a href="https://github.com/alfredwesterveld/php-auth" rel="nofollow noreferrer">https://github.com/alfredwesterveld/php-auth</a></p> <p>Also I would advice you to look into <a href="http://net.tutsplus.com/tutorials/php/why-you-should-be-using-phps-pdo-for-database-access/" rel="nofollow noreferrer">PDO</a> to do safe/fast cross-database SQL.</p>
    singulars
    1. This table or related slice is empty.
    1. PORegistration Security PHP
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USAlfred
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORegistration Security PHP
      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. VTAcceptedByOriginator
    1. CO-1 for the "never store pwds in a db" (OpenID is a confusing failure), +1 for phpass (secure password generation), so it's a wash.
      singulars
      1. PO
      1. USeykanal
    2. COlol eykanal you succeeded at stackoverflow, because stackoverflow requires openID. I don't understand that people find it difficult to login with openID. It is simple as hell. Please check out my demo at http://westerveld.name/php-openid/ and login with for example google or myopenID. It is so easy...
      singulars
      1. PO
      1. USAlfred
    3. COOpenID is a failure from the point of view of the consumer, not the developer. It's no surprise that a developer-oriented site like SO uses it with little problem, but for consumers it [solves a problem they never had](http://www.quora.com/OpenID/What-s-wrong-with-OpenID), and confuses the hell out of them while doing so. That post describes the problems quite nicely.
      singulars
      1. PO
      1. USeykanal
 

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