LEFT JOIN
Понятно про анализ данных, технологии, нейросети и, конечно, SQL. Услуги — leftjoin.ru Курсы по аналитике — https://stepik.org/users/431992492 Автор — @valiotti Реклама — @valiotti Перечень РКН: https://tapthe.link/PpkTHavwS
Show more📈 Analytical overview of Telegram channel LEFT JOIN
Channel LEFT JOIN (@leftjoin) in the Russian language segment is an active participant. Currently, the community unites 43 027 subscribers, ranking 3 127 in the Technologies & Applications category and 14 793 in the Russia region.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 43 027 subscribers.
According to the latest data from 30 June, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by -754 over the last 30 days and by -16 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 17.50%. Within the first 24 hours after publication, content typically collects 11.62% reactions from the total number of subscribers.
- Post reach: On average, each post receives 7 528 views. Within the first day, a publication typically gains 5 001 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 18.
- Thematic interests: Content is focused on key topics such as аналитика, sql, данными, datalens, csv.
📝 Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
“Понятно про анализ данных, технологии, нейросети и, конечно, SQL.
Услуги — leftjoin.ru
Курсы по аналитике — https://stepik.org/users/431992492
Автор — @valiotti
Реклама — @valiotti
Перечень РКН: https://tapthe.link/PpkTHavwS”
Thanks to the high frequency of updates (latest data received on 01 July, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.
SELECT TOP 20
title,
country,
AVG(salary) AS average_salary,
SUM(salary) AS sum_salary,
AVG(salary + payroll_tax) AS average_gross_salary,
SUM(salary + payroll_tax) AS sum_gross_salary,
AVG(salary + payroll_tax + benefits_cost) AS average_gross_cost,
SUM(salary + payroll_tax + benefits_cost) AS sum_gross_cost,
COUNT(*) as count
FROM employees
WHERE salary + payroll_tax + benefits_cost > 0 AND country = 'USA'
GROUP BY title, country
ORDER BY sum_gross_cost
HAVING count > 200
запрос на PRQL будет выглядеть так:
from employees
filter country = "USA"
let gross_salary = salary + payroll_tax
let gross_cost = gross_salary + benefits_cost
filter gross_cost > 0
aggregate by:[title, country] [
average salary,
sum salary,
average gross_salary,
sum gross_salary,
average gross_cost,
sum gross_cost,
count,
]
sort sum_gross_cost
filter count > 200
take 20
ИМХО, не выглядит существенно удобнее / читаемее. А вы как считаете?
2. Malloy — другая попытка заменить SQL от Looker (однако есть примечание, что этот эксперимент без поддержки Google).
Запрос выглядит вот так:
query: table('malloy-data.faa.flights') -> {
where: origin: 'SFO'
group_by: carrier
aggregate: [
flight_count is count()
average_flight_time is flight_time.avg()
]
}
В общем, резюме: каждая метла метет по своему 🥸
А как вам эти варианты замены SQL, что думаете?
Available now! Telegram Research 2025 — the year's key insights 
