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. This table or related slice is empty.
    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. COThanks for the reply. Well, as it is now, I have a query that checks the `friendships` table for an existing, valid match between two users. If the number of rows found is not zero, then a friendship is determined. To use the local array method, I'd need to change my query to pull all valid friendship matches from the table, and then test against that. I realize now that the array idea is less efficient. However, it brought up a question I have. Does there come a point in which you can query the database too often, or does that not really matter?
      singulars
    2. COMy take on that is that database query is getting cheaper, cpu power is getting cheaper. Basically, the capabilities of computers are getting cheaper every day. So the first thing you should be concerned with is to do the right thing. Get it working with the correct logic first. Then see if it needs to be optimised. If it runs fast without any optimisation, then you have just saves a lot of time. If it runs show, at least your codes are easily understood by anyone, because there is no weird logic to attempt to speed up the codes. It will make the codes easier to maintain and to optimise.
      singulars
    3. COYou will most likely need to write the codes, then bench mark it against real live conditions, then you can decide if the number of queries are too much. But as a rule of thumb, I try to stop at 50 queries per PHP page.
      singulars
 

Querying!

 
Guidance

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