Note that there are some explanatory texts on larger screens.

plurals
  1. POmerging two SELECT queries
    primarykey
    data
    text
    singulars
    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. CODid you mean `data` or `date` in your last query? Also, if you are not selecting any data from the URL table, do you really need to join to it? (The answer could be "yes, to ensure that there is a URL entry for that user ID".) And why so many back-ticks; it is as bad as MS SQL Server and square brackets!
      singulars
    2. COI've written the query on the way, so I naturally left few mistakes. You are right though, it had to be `date` not `data`. I'd normally ignore a remark about `back-ticks`, though you have quite high reputation, so I am kinda curious why you are saying that "it is as bad as MS SQL Server and square brackets"? The purpose itself of backticks is to ensure that MySQL server is able to quickly identify table and column names and to avoid confusion when using reserved keywords, like `left` or `right` in nested sets.
      singulars
    3. COThe same claim is made for square brackets by MS SQL Server users. It looks ugly to me and it is wholly non-standard. No other DBMS supports back-ticks or square brackets for what the SQL standard calls 'delimited identifiers', which the standard says are enclosed in double quotes; single quotes are reserved for strings. Different DBMS have different rules for where you can use keywords. The one I use mostly allows keywords as identifiers in many places. It's best to avoid the quotes by avoiding keywords as identifiers.
      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