Telegram RegisterThe public register of Telegram
Telegram profile photo for Senior SQL Developer

Channel

Senior SQL Developer

@seniorsql

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

14,129subscribers

-351 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001468396285
TypeChannel
Username@seniorsql
Description№ 4931128435 Изучаем SQL. По вопросам сотрудничества: @adv_and_pr
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held61
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/seniorsql

Topic

Technology — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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 the other topics.

Growth

14,12914,48014,304.57 August 202617 November 2026
61 measurements spanning 102 days, net -351. 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 14,076–14,533 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)SubscribersChange
17 Nov 2026, 03:3914,129-11
13 Nov 2026, 20:4614,140-11
11 Nov 2026, 01:4614,151-1
9 Nov 2026, 09:0914,152-6
8 Nov 2026, 00:0514,158-9
6 Nov 2026, 20:1914,167-5
5 Nov 2026, 18:4614,172-4
4 Nov 2026, 21:1614,176-4
3 Nov 2026, 18:2514,180-10
2 Nov 2026, 14:5714,190-4
1 Nov 2026, 14:1814,194-4
31 Oct 2026, 17:5014,198-5
30 Oct 2026, 15:5614,203-4
29 Oct 2026, 12:3614,207-2
28 Oct 2026, 10:0114,209-3
27 Oct 2026, 08:2714,212-4
26 Oct 2026, 08:4814,216-10
25 Oct 2026, 06:4614,226-10
24 Oct 2026, 07:2714,236-1
23 Oct 2026, 09:5114,237first reading

Engagement

65 posts held, back to 6 July 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 81 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
7.43%
avg views ÷ 14,129 subscribers
Avg views / post
1,050
28 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
28
of 65 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 16 November 2026
Posts held65 (6 July 2026 – 16 November 2026)
Views total29,390
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 08:27 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
≈1,260
Videos
≈2
Links
≈524

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 28 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 20:50 UTC405 viewsread 17 November 2026

Как можно оптимизировать выполнение запроса с использованием коррелированного подзапроса, чтобы улучшить производительность на больших объемах данных? Один из эффективных способов оптимизации — преобразование коррелированного подзапроса в JOIN. Коррелированный подзапрос выполняется для каждой строки внешнего запроса, что может быть неэффективно на больших наборах данных. Использование JOIN позволяет базе данных обра…

13 Nov 2026, 20:58 UTC714 viewsread 17 November 2026
Photo

Функция FIELD() Функция FIELD() возвращает индексную позицию значения в списке значений. Эта функция выполняет поиск без учета регистра. Примечание: Если указанное значение не найдено в списке значений, то эта функция вернет 0. Если значение равно NULL, то эта функция вернет 0. Синтаксис: FIELD(value, val1, val2, val3, ...).

12 Nov 2026, 20:16 UTC785 viewsread 17 November 2026
Photo

Функция REVERSE() Функция REVERSE() переворачивает строку и возвращает результат.

11 Nov 2026, 20:26 UTC854 viewsread 17 November 2026

#вопросы_с_собеседований Расскажите алгоритм решения следующей задачи Предположим, у вас есть две таблицы: Orders (Заказы) и Customers (Клиенты). Таблица Orders содержит колонки OrderID, CustomerID и OrderDate, а таблица Customers содержит CustomerID, Name и Country. Как бы вы нашли имена всех клиентов из США, которые не сделали ни одного заказа после 1 января 2022 года? Для решения этой задачи можно использовать п…

10 Nov 2026, 20:49 UTC909 viewsread 17 November 2026
Photo

Объяснение Запроса Подзапрос: Здесь используется подзапрос для выбора CustomerID из таблицы Orders, группируя по CustomerID и применяя условие HAVING COUNT(OrderID) > 2. Это выбирает клиентов, сделавших более двух заказов. Объединение (JOIN): Основной запрос использует JOIN для соединения таблиц Customers и результата подзапроса по CustomerID. Условие WHERE: Фильтрация происходит по полю City в таблице Customers, ч…

9 Nov 2026, 20:52 UTC896 viewsread 17 November 2026
Photo

Очистите все таблицы базы данных test1 Ответ на картинке.

8 Nov 2026, 20:22 UTC918 viewsread 17 November 2026
Photo

#вопросы_с_собеседований При выборке из таблицы workers выведите дату в формате '31.12.2025' Ответ на картинке.

6 Nov 2026, 19:45 UTC≈1,090 viewsread 17 November 2026

#вопросы_с_собеседований Какая польза от функции NVL()? Функция NVL() является частью базы данных Oracle и преобразует значение NULL в другие значения. В SQL Server, эквивалентная функция - ISNULL(), а MySQL - IFNULL().

5 Nov 2026, 20:59 UTC≈1,140 viewsread 17 November 2026
Photo

ORDER BY ORDER BY используется для сортировки результатов запроса по убыванию или возрастанию. ORDER BY отсортирует по возрастанию, если не будет указан способ сортировки ASC или DESC. Рассмотрим пример: Выведем список курсов по возрастанию и убыванию количества кредитов.

4 Nov 2026, 19:53 UTC≈1,100 viewsread 17 November 2026

Решаем загадку Джиндоша на SQL в пять строчек Смотреть статью

3 Nov 2026, 20:26 UTC≈1,000 viewsread 17 November 2026

#вопросы_с_собеседований Как работают подстановочные знаки? Это специальные символы, которые нужны для замены каких-либо знаков в запросе. Они используются вместе с оператором LIKE, с помощью которого можно отфильтровать запрашиваемые данные.

2 Nov 2026, 19:58 UTC≈1,060 viewsread 17 November 2026
Photo

Функция DAYNAME() Функция DAYNAME() возвращает имя дня недели для заданной даты. Синтаксис: DAYNAME(date).

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

Posts recorded as deleted after publishing

We recorded 1 post on @seniorsql as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
26 August 2026
Most recent seen missing
26 August 2026
Median time before seen missing
3 days
Seen missing in the last 30 days
0

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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.

Базы данных | Access, SQL, Big Data
@databases_secrets · 29,986
Telegram ranks this channel #24 of 82 here — alongside 81 others — read 7 September 2026
Senior Java Developer
@seniorjavist · 20,341
Telegram ranks this channel #51 of 89 here — alongside 88 others — read 26 September 2026
Senior Python Developer
@seniorpy · 39,056
Telegram ranks this channel #58 of 92 here — alongside 91 others — read 30 August 2026
IT сфера * Компьютеры * Технологии
@it_kanal_tg · 26,614
Telegram ranks this channel #71 of 79 here — alongside 78 others — read 13 September 2026
Python Learning
@Python_per_month · 27,837
Telegram ranks this channel #71 of 86 here — alongside 85 others — read 9 September 2026
Senior Frontend Developer | JavaScript, React, HTML & CSS
@senior_front · 18,852
Telegram ranks this channel #90 of 90 here — alongside 89 others — read 2 October 2026

This channel appears in 6 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 17 November 2026 — this entry's latest reading, not the date you are reading this.

“Senior SQL Developer” (@seniorsql), 14,129 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/seniorsql.

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.