Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The one mistake I did in the beginning of my programming days, is not use a database class there are many out there, i have one that i have added to over the years, but this will speed up your development time. As far as database goes there are so many rules and things you learn with trial and error... the internet is a great resource. SQL is pretty easy to pick up. </p> <p>I dont know what your level is so ill go over some basics that i know of...</p> <p>I would say a few do's and don'ts <strong>Dont</strong> name your database, tables, &amp; columns common names ie "users", "products" come up with your own naming structure something like </p> <p>database : prod_dbb9 table : tbb_users column : u_uid, u_userid</p> <p>This will prevent someone from guessing your tables or database structure and allow you to hack your db. </p> <p>Sql injection is pretty easy to do... so always escape your sql commands to the database! PHP has a built in function for that <strong>mysql_real_escape_string</strong></p> <p>always remember ID numbers are easier on the database than text so if you can pull records by id numbers </p> <p>ie: profile.php?id=123 rather than profile.php?username=jason</p> <p>Kind of obvious but don't name your querystrings the same as your columns in your db ie</p> <p>profile.php?u_userid=123</p> <p>If you are deletin only one record make sure to put "limit 1" at the end of your SQL this will help prevent more records from getting deleted by hackers. </p> <p>Always encrypt your users passwords. You can choose to use php MD5() but be aware that this is one way encryption...(no one can ever see this password again) so if your user forgets their password you will have to generate them a new password and mail it to them... </p> <p>Well thats all i got for now.. good luck!</p> <ul> <li>Jason</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow do i structure my SQL Database (tables, Schemas, users, stored procedures etc.) to prepare it for an n-tier architecture?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USjason
    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. VTDownMod
    1. COvery nice and elaborate answer. +1 for having the patience to write it but I'm more interested in the database itself and it's structure
      singulars
      1. PO
      1. USAlexRednic
    2. COi'd say to **do** name your database entities with suggestive names otherwise the dba or other developers will probably kill you. since you have a business layer in front of your db it's very unlikely that someone will guess its structure.
      singulars
      1. PO
      1. USdevnull
    3. CO-1 for a lot of inpractical stuff that would be "breaking convenstions" in pretty much all projects I ever was in. I agree with devnull - name items sensible. Dont care abot hackers there. Use schemata to isolate your items. Don't assume SQL means mySQL ;)
      singulars
      1. PO
      1. USTomTom
 

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