Off-by-one on range boundaries
Wrong move: Loop endpoints miss first/last candidate.
Usually fails on: Fails on minimal arrays and exact-boundary answers.
Fix: Re-derive loops from inclusive/exclusive ranges before coding.
Build confidence with an intuition-first walkthrough focused on core interview patterns fundamentals.
Table: Views
+---------------+---------+ | Column Name | Type | +---------------+---------+ | article_id | int | | author_id | int | | viewer_id | int | | view_date | date | +---------------+---------+ There is no primary key (column with unique values) for this table, the table may have duplicate rows. Each row of this table indicates that some viewer viewed an article (written by some author) on some date. Note that equal author_id and viewer_id indicate the same person.
Write a solution to find all the authors that viewed at least one of their own articles.
Return the result table sorted by id in ascending order.
The result format is in the following example.
Example 1:
Input: Views table: +------------+-----------+-----------+------------+ | article_id | author_id | viewer_id | view_date | +------------+-----------+-----------+------------+ | 1 | 3 | 5 | 2019-08-01 | | 1 | 3 | 6 | 2019-08-02 | | 2 | 7 | 7 | 2019-08-01 | | 2 | 7 | 6 | 2019-08-02 | | 4 | 7 | 1 | 2019-07-22 | | 3 | 4 | 4 | 2019-07-21 | | 3 | 4 | 4 | 2019-07-21 | +------------+-----------+-----------+------------+ Output: +------+ | id | +------+ | 4 | | 7 | +------+
Problem summary: Table: Views +---------------+---------+ | Column Name | Type | +---------------+---------+ | article_id | int | | author_id | int | | viewer_id | int | | view_date | date | +---------------+---------+ There is no primary key (column with unique values) for this table, the table may have duplicate rows. Each row of this table indicates that some viewer viewed an article (written by some author) on some date. Note that equal author_id and viewer_id indicate the same person. Write a solution to find all the authors that viewed at least one of their own articles. Return the result table sorted by id in ascending order. The result format is in the following example.
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: General problem-solving
{"headers":{"Views":["article_id","author_id","viewer_id","view_date"]},"rows":{"Views":[[1,3,5,"2019-08-01"],[1,3,6,"2019-08-02"],[2,7,7,"2019-08-01"],[2,7,6,"2019-08-02"],[4,7,1,"2019-07-22"],[3,4,4,"2019-07-21"],[3,4,4,"2019-07-21"]]}}Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #1148: Article Views I
// Auto-generated Java example from rust.
class Solution {
public void exampleSolution() {
}
}
// Reference (rust):
// // Accepted solution for LeetCode #1148: Article Views I
// pub fn sql_example() -> &'static str {
// r#"
// -- Accepted solution for LeetCode #1148: Article Views I
// # Write your MySQL query statement below
// SELECT DISTINCT author_id AS id
// FROM Views
// WHERE author_id = viewer_id
// ORDER BY 1;
// "#
// }
// Accepted solution for LeetCode #1148: Article Views I
// Auto-generated Go example from rust.
func exampleSolution() {
}
// Reference (rust):
// // Accepted solution for LeetCode #1148: Article Views I
// pub fn sql_example() -> &'static str {
// r#"
// -- Accepted solution for LeetCode #1148: Article Views I
// # Write your MySQL query statement below
// SELECT DISTINCT author_id AS id
// FROM Views
// WHERE author_id = viewer_id
// ORDER BY 1;
// "#
// }
# Accepted solution for LeetCode #1148: Article Views I
# Auto-generated Python example from rust.
def example_solution() -> None:
return
# Reference (rust):
# // Accepted solution for LeetCode #1148: Article Views I
# pub fn sql_example() -> &'static str {
# r#"
# -- Accepted solution for LeetCode #1148: Article Views I
# # Write your MySQL query statement below
# SELECT DISTINCT author_id AS id
# FROM Views
# WHERE author_id = viewer_id
# ORDER BY 1;
# "#
# }
// Accepted solution for LeetCode #1148: Article Views I
pub fn sql_example() -> &'static str {
r#"
-- Accepted solution for LeetCode #1148: Article Views I
# Write your MySQL query statement below
SELECT DISTINCT author_id AS id
FROM Views
WHERE author_id = viewer_id
ORDER BY 1;
"#
}
// Accepted solution for LeetCode #1148: Article Views I
// Auto-generated TypeScript example from rust.
function exampleSolution(): void {
}
// Reference (rust):
// // Accepted solution for LeetCode #1148: Article Views I
// pub fn sql_example() -> &'static str {
// r#"
// -- Accepted solution for LeetCode #1148: Article Views I
// # Write your MySQL query statement below
// SELECT DISTINCT author_id AS id
// FROM Views
// WHERE author_id = viewer_id
// ORDER BY 1;
// "#
// }
Use this to step through a reusable interview workflow for this problem.
Two nested loops check every pair or subarray. The outer loop fixes a starting point, the inner loop extends or searches. For n elements this gives up to n²/2 operations. No extra space, but the quadratic time is prohibitive for large inputs.
Most array problems have an O(n²) brute force (nested loops) and an O(n) optimal (single pass with clever state tracking). The key is identifying what information to maintain as you scan: a running max, a prefix sum, a hash map of seen values, or two pointers.
Review these before coding to avoid predictable interview regressions.
Wrong move: Loop endpoints miss first/last candidate.
Usually fails on: Fails on minimal arrays and exact-boundary answers.
Fix: Re-derive loops from inclusive/exclusive ranges before coding.