Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POPHP and PostgreSQL, best practice to register a new user in the database?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USmax
    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
    1. COYou wrote: "Spreading the data across several schemas will make it impossible to do effective queries with no real benefit". I can't see how? I think it's the other way around. In my webapp, I use objects that holds references to other objects. I have to fetch the component ID:s and put them into other queries to successfully build together complete objects. Mixing in the use of user ID would only complicate matters. The way I see it, schemas are a perfect balance between the standard way of doing it (user table and ID columns) and the more extreme to create a new database for every user.
      singulars
      1. PO
      1. USMartin Andersson
    2. COTry writing a query to fetch a user by email for example. What you are describing works well for document databases such as MongoDB, CouchDB or Jackrabbit, but is a poor fit for relational databases.
      singulars
      1. PO
      1. USmax
    3. COApprechiate your answers papirtiger. Still, if I wanted to run a query to get a user by his e-mail, I'd query the admin database I mentioned in my first post (the question). I intend to keep all "metadata" about the users in the admin database, neetly packed into just a few tables. There I will store their usernames, e-mails, and not the least the schema name used in the other database. This other database will only store user specific data needed by the core of the application. And as I said earlier, this user specific data are quite complicated stuff with their own interrelated IDs.
      singulars
      1. PO
      1. USMartin Andersson
 

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