Telegram RegisterThe public register of Telegram
Telegram profile photo for SQL и БД Learning

Channel

SQL и БД Learning

@sql_tg

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry

9,604subscribers

-42 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001792078958
TypeChannel
Username@sql_tg
Description№ 5060218708 Изучаем SQL с нуля По всем вопросам @mascarov_valentin Реклама на бирже - https://telega.in/c/SQl_and_DB_Learning
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live23 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/sql_tg

Growth

9,6049,6469,6257 August 2026 — 9,646 subscribers7 August 2026 — 9,646 subscribers8 August 2026 — 9,641 subscribers11 August 2026 — 9,628 subscribers14 August 2026 — 9,616 subscribers17 August 2026 — 9,615 subscribers20 August 2026 — 9,609 subscribers23 August 2026 — 9,604 subscribers7 August 202623 August 2026
8 measurements spanning 16 days, net -42. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 9,598–9,652 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 11:599,604-5
20 Aug 2026, 07:129,609-6
17 Aug 2026, 16:169,615-1
14 Aug 2026, 17:569,616-12
11 Aug 2026, 10:469,628-13
8 Aug 2026, 00:539,641-5
7 Aug 2026, 04:459,646no change
7 Aug 2026, 04:349,646first reading

Engagement

20 posts held, back to 30 December 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 26 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.14%
avg views ÷ 9,604 subscribers
Avg views / post
590
1 post measured
Reaction rate
0.169%
reactions ÷ views · ER floor
Posts in window
1
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 August 2026
Posts held20 (30 December 202517 August 2026)
Views total590
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Aug 2026, 23:47 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.

What this channel posts

Photos
808
Videos
9
Links
450

Lifetime counters from Telegram’s own channel header, read 23 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

90 reactions across 19 posts, in 3 distinct kinds. The most used accounts for 82.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍7482.2%
🎄1112.2%
🔥55.56%

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 19 of the 20 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 90reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 30 December 2025 to 17 August 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.

Recent posts

17 Aug 2026, 17:12 UTC590 views1 reactionsread 23 August 2026

Не все типы репликации одинаково полезны, или почему две MySQL лучше одной Смотреть статью

👍1

23 Jul 2026, 09:08 UTC≈1,130 viewsread 23 August 2026

MySQL ускорение SQL запросов Ускорение SQL запросов в MySQL может быть достигнуто следующими способами: 1. Индексы: использование индексов может ускорить поиск и сортировку данных в ваших таблицах. 2. Оптимизация структуры таблиц: важно убедиться, что структура таблиц оптимизирована для выполнения запросов. 3. Оптимизация запросов: проверьте ваши запросы на оптимизацию, убедитесь, что вы используете правильные оп

11 Jul 2026, 17:58 UTC≈1,350 views3 reactionsread 23 August 2026
Video

🖥 Google почти всегда задает вопросы по SQL во время собеседований на вакансии Data Analytics, Data Science и Data Engineering. Поэтому, если вы готовитесь к собеседованию по SQL, решите эти 11 РЕАЛЬНЫХ вопросов для собеседования Google по SQL. https://datalemur.com/blog/google-sql-interview-questions

👍3

9 Jul 2026, 14:51 UTC≈1,340 views2 reactionsread 23 August 2026

Концепция ORM как двигатель прогресса — выдержит ли ее ваша СУБД? Смотреть статью

👍2

2 Jul 2026, 14:02 UTC≈1,490 views3 reactionsread 23 August 2026
Photo

#вопросы_с_собеседований Как распарсить строку в SQL? Часто возникает необходимость распарсить строку в SQL запросе, чтобы получить отдельные элементы. Существует несколько способов это сделать. 1. Использование функции SUBSTRING Для извлечения отдельных элементов из строки можно использовать функцию SUBSTRING. 2. Использование функции CHARINDEX Для извлечения подстроки из строки можно использовать функцию CHAR

👍3

17 Jun 2026, 15:39 UTC≈1,510 views4 reactionsread 23 August 2026

MySQL ускорение SQL запросов Ускорение SQL запросов в MySQL может быть достигнуто следующими способами: 1. Индексы: использование индексов может ускорить поиск и сортировку данных в ваших таблицах. 2. Оптимизация структуры таблиц: важно убедиться, что структура таблиц оптимизирована для выполнения запросов. 3. Оптимизация запросов: проверьте ваши запросы на оптимизацию, убедитесь, что вы используете правильные оп

👍4

28 May 2026, 08:55 UTC≈1,670 views2 reactionsread 23 August 2026
Video

🖥 Google почти всегда задает вопросы по SQL во время собеседований на вакансии Data Analytics, Data Science и Data Engineering. Поэтому, если вы готовитесь к собеседованию по SQL, решите эти 11 РЕАЛЬНЫХ вопросов для собеседования Google по SQL. https://datalemur.com/blog/google-sql-interview-questions

👍2

18 May 2026, 13:56 UTC≈2,090 views3 reactionsread 23 August 2026
Photo

💻Knex.js — конструктор SQL-запросов для PostgreSQL и других СУБД — npm install knex --save — npm install pg --save Knex.js спроектирован как гибкий и портативный инструмент. В нем есть как традиционные колбеки, так и интерфейс промисов для более чистого управления потоком async, потоковый интерфейс, полнофункциональные конструкторы запросов и схем, поддержка транзакций (с точками сохранения), пул соединений и ст

👍2🔥1

4 May 2026, 17:18 UTC≈1,970 views2 reactionsread 23 August 2026

Как ускорить базу данных при помощи шардирования Смотреть статью

👍1🔥1

27 Apr 2026, 16:41 UTC≈2,110 views7 reactionsread 23 August 2026
Photo

Поиск значений в таблице, которые не совпадают с другой таблицей Для выполнения поиска значений в таблице, которые не совпадают с другой таблицей в SQL, можно использовать операторы JOIN, NOT IN и NOT EXISTS. 1. JOIN - используется для объединения двух таблиц по заданному условию. Для поиска значений, которые не совпадают, можно использовать LEFT JOIN или RIGHT JOIN, а затем выбрать строки с NULL значениями в стол

👍7

12 Apr 2026, 19:23 UTC≈2,050 views8 reactionsread 23 August 2026
Photo

Все о jsonb_to_recordset в SQL Функция jsonb_to_recordset в SQL используется для преобразования данных, хранящихся в формате JSON, в таблицы. Она позволяет распаковывать массивы и объекты JSON и превращать их в строки и столбцы в таблице. Кроме того, jsonb_to_recordset позволяет работать с вложенными объектами и массивами. Для этого нужно использовать функцию jsonb_each, которая распаковывает объекты и массивы JSON

👍8

19 Mar 2026, 14:52 UTC≈2,580 views4 reactionsread 23 August 2026
Photo

REPLICATE в SQL Server REPLICATE - это функция в SQL Server, которая повторяет входную строку указанное количество раз. Эта функция может быть полезна во многих сценариях, например, при создании тестовых данных или при форматировании вывода. Синтаксис функции REPLICATE выглядит следующим образом: REPLICATE ( string_expression , integer_expression ) - string_expression - это строковое выражение, которое нужно повто

👍4

Showing the 12 most recent of 20 posts we hold for @sql_tg. 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.

Appears in Telegram’s recommendations for other channels

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.

Python обучающий
@pythonist24 · 56,254
Telegram ranks this channel #63 of 88 here — alongside 87 others — read 23 August 2026
Однажды в трендах
@trendo · 68,975
Telegram ranks this channel #75 of 90 here — alongside 89 others — read 20 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“SQL и БД Learning” (@sql_tg), 9,604 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/sql_tg.

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.