Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>So let me get this right, you want to store this list so it isn't queried on each page?</p> <p>First I would recommend you only perform this query on pages that need this data and second I would say that on these pages you don't try this.</p> <p>Imagine a user stops following or starts following. Some complex cache calculator or event bubbler programmed into your own PHP app to purge the foreign session of data (which is bad, the user has access to data that is not their own, a session infact) could be tiedious with security and performance.</p> <p>The better thing to do is to perform the query again for each new page. This would be much easier, probably more performant and wouldn't be micro-optimising.</p> <h2>Edit</h2> <p>If you are picking out 10k rows on one page then you might be doing something wrong. You might be looking at it from the wrong perspective.</p>
    singulars
    1. This table or related slice is empty.
    1. POStoring users 'following' during a PHP session
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USSammaye
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POStoring users 'following' during a PHP session
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou are correct that is exactly what I want to do. Every page unfortunately, will require this query to be run since every page shows some detail about other users... The logic is already in place to update the array that is stored in memcached without completely destroying the cache therefore applying it to an array stored in the app itself would be trivial. Regardless thanks, I'm looking for opinions either way on this, as like you said, it may be completely unneeded.
      singulars
      1. PO
      1. USgordyr
    2. CO@gordyr Having made a lot of scalable apps myself and even worked on a couple of high profile apps I have never seen memcached used in this way efficiently. Normally it is used to house SQL result sets (or other data that is rare modified) instead of querying directly but it seems like you wanna take it a step further and have memcache somehow trace changes without pinging SQL...it sounds undoable.
      singulars
      1. PO
      1. USSammaye
    3. COThanks this is useful info. What I am trying to do is prepare this app to be as scale-able as possible. My thought process is as follows: In this app user's do not frequently add/remove followers, most of their time will be spent using the app itself. Therefore storing these results in memcached appears to make sense as they are small arrays of userid's. Would performing a query on a table with for e.g 10 million rows extracting that users list of followers several times during a users session be acceptable? Please forgive my ignorance I have never had to deal with such large dataset
      singulars
      1. PO
      1. USgordyr
 

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