📚 Скидка к началу учёбы Обещал себе выучить SQL «с сентября»? Вот и сентябрь. По промокоду SEPT26 — минус 25% на премиум до 4 сентября.
🔥7❤2👍2

Channel
@sqlacademyofficial
On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
11,766subscribers
+213 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001852630630 |
|---|---|
| Type | Channel |
| Username | @sqlacademyofficial |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/sqlacademyofficial |
Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 94% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 09:58 | 11,766 | +50 |
| 19 Sept 2026, 13:18 | 11,716 | +11 |
| 17 Sept 2026, 05:16 | 11,705 | +11 |
| 13 Sept 2026, 18:19 | 11,694 | +7 |
| 12 Sept 2026, 01:19 | 11,687 | +5 |
| 9 Sept 2026, 18:36 | 11,682 | +40 |
| 6 Sept 2026, 09:40 | 11,642 | +5 |
| 4 Sept 2026, 02:17 | 11,637 | +13 |
| 2 Sept 2026, 16:55 | 11,624 | +5 |
| 1 Sept 2026, 13:26 | 11,619 | -10 |
| 31 Aug 2026, 15:18 | 11,629 | -2 |
| 30 Aug 2026, 14:05 | 11,631 | -1 |
| 28 Aug 2026, 18:14 | 11,632 | +2 |
| 27 Aug 2026, 20:13 | 11,630 | +10 |
| 26 Aug 2026, 17:13 | 11,620 | -6 |
| 25 Aug 2026, 18:24 | 11,626 | +6 |
| 24 Aug 2026, 19:35 | 11,620 | +2 |
| 23 Aug 2026, 02:25 | 11,618 | +6 |
| 21 Aug 2026, 13:13 | 11,612 | -3 |
| 20 Aug 2026, 16:12 | 11,615 | first reading |
26 posts held, back to 21 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 46 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 1 September 2026 |
|---|---|
| Posts held | 26 (21 May 2026 – 1 September 2026) |
| Views total | 4,390 |
| Reactions total | 29 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 23:42 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
622 reactions across 18 posts, in 8 distinct kinds. The most used accounts for 44.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 276 | 44.4% | |
| 🔥 | 170 | 27.3% | |
| ❤ | 140 | 22.5% | |
| 🤯 | 25 | 4.02% | |
| 👌 | 5 | 0.804% | |
| 🗿 | 3 | 0.482% | |
| 🙏 | 2 | 0.322% | |
| 👎 | 1 | 0.161% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 18 of the 26 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 622 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 26 most recent posts we hold, published 21 May 2026 to 1 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
📚 Скидка к началу учёбы Обещал себе выучить SQL «с сентября»? Вот и сентябрь. По промокоду SEPT26 — минус 25% на премиум до 4 сентября.
🔥7❤2👍2
Photo, posted without a caption
🪓 Убили индекс одной функцией: почему YEAR(date) тормозит базу Ты создал идеальный индекс по дате, но запрос всё равно работает целую вечность. Причина кроется всего в одной функции. ⚙️ Почему база игнорирует индекс 🔹 Как только ты пишешь WHERE YEAR(order_date) = 2023, база перестаёт видеть исходные значения дат. 🔹 Она не может искать по индексу (как по алфавитному указателю в книге), потому что ей нужно сначала вы…
❤9👍6🔥3
🛑 Как Materialized View может повесить продакшен Ты создал материализованное представление, чтобы ускорить тяжёлые запросы. Но в момент обновления данных приложение вдруг замирает, а пользователи видят бесконечную загрузку. ⚙️ Почему всё зависло Обычная команда REFRESH MATERIALIZED VIEW работает очень грубо. 🔹 Она вешает эксклюзивную блокировку. База полностью запрещает чтение, пока собирает новые данные. Это как з…
👍10🔥3🤯2
Photo, posted without a caption
Photo, posted without a caption
🙈 Повесил индекс, а база его игнорит Ты создал индекс на колонку status, запускаешь поиск, а EXPLAIN нагло выдаёт Seq Scan. Кажется, база сломалась, но на самом деле она спасает твоё время. ⚙️ Почему это происходит Индекс работает как алфавитный указатель в конце книги. Он идеален, если тебе нужно найти 5 строк из миллиона. База быстро находит ссылки и точечно забирает данные. 📉 Когда Full Scan быстрее Если ты ище…
👍10❤3🔥2🗿2
🤡 Иллюзия оптимизации: индекс на is_active только вредит Кажется логичным: если в запросах часто есть WHERE is_active = true, на эту колонку нужен индекс. Но на деле база его проигнорирует, а ты лишь замедлишь работу системы. ⚙️ Почему база его не использует Индексу важно разнообразие значений (кардинальность). Представь предметный указатель в конце книги: если слово встречается на 90% страниц, проще пролистать всю…
❤13👍11🤯3
Photo, posted without a caption
🪤 Ловушка Foreign Key: почему удаление строки вешает базу Ты удаляешь одного пользователя, а внезапно зависает весь проект. Если ты работаешь в PostgreSQL, обычный внешний ключ может стать причиной жесткой блокировки. ⚙️ В чём подвох? Многие уверены, что FOREIGN KEY автоматически создаёт индекс на колонку связи. 🔹 В MySQL это действительно так. 🔹 А вот в PostgreSQL — нет. Индекс нужно создавать вручную. 📉 Что прои…
🔥20❤8👍4
Photo, posted without a caption
🧮 Математика с подвохом: почему сложение обнуляет зарплату, а SUM() — нет Считаешь итоговую выплату сотруднику как salary + bonus? Если премии нет (в базе лежит NULL), математика сыграет злую шутку, и человек останется вообще без денег в итоговом отчёте. ⚠️ Ловушка прямого сложения 🔹 NULL — это не ноль, а полная «неизвестность». 🔹 Любая математическая операция с неизвестностью заражает итог. Если оклад 1000, а бону…
👍38❤7🤯5🔥1
Showing the 12 most recent of 26 posts we hold for @sqlacademyofficial. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 26 September 2026 — this entry's latest reading, not the date you are reading this.
“SQL Academy: всё о реляционных БД и SQL” (@sqlacademyofficial), 11,766 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/sqlacademyofficial.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.