Channel
@databases_secrets
On this record: Growth · Engagement · What this channel posts · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
30,120subscribers
-26 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001247460025 |
|---|---|
| Type | Channel |
| Username | @databases_secrets |
| Description | Всё о базах данных простым языком. Сотрудничество: @max_excel РКН: vk.cc/cHhG5h |
| Created | 19 October 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/databases_secrets |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 20:02 | 30,120 | -4 |
| 21 Aug 2026, 11:27 | 30,124 | -12 |
| 20 Aug 2026, 12:46 | 30,136 | -1 |
| 19 Aug 2026, 14:23 | 30,137 | -5 |
| 18 Aug 2026, 17:08 | 30,142 | -7 |
| 17 Aug 2026, 15:55 | 30,149 | -2 |
| 16 Aug 2026, 06:07 | 30,151 | -2 |
| 14 Aug 2026, 17:37 | 30,153 | -5 |
| 12 Aug 2026, 02:02 | 30,158 | -8 |
| 10 Aug 2026, 00:29 | 30,166 | -2 |
| 9 Aug 2026, 02:37 | 30,168 | +29 |
| 8 Aug 2026, 01:25 | 30,139 | -7 |
| 6 Aug 2026, 09:00 | 30,146 | no change |
| 6 Aug 2026, 08:54 | 30,146 | first reading |
45 posts held, back to 12 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 42 pagesof 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.
| Window | Rolling 30 days · latest post in window 22 August 2026 |
|---|---|
| Posts held | 45 (12 July 2026 – 22 August 2026) |
| Views total | 57,147 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Aug 2026, 18:07 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.
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.
Measured directly from 10 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VtzquuHE37 | 1 | 18 August 2026 | 18 August 2026 |
| 2VtzqvwZuK1 | 1 | 20 August 2026 | 20 August 2026 |
| 2W5zFJrnN6u | 1 | 18 August 2026 | 18 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 45 most recent posts we hold, published 12 July 2026 to 22 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Основы SQL: Подзапросы В этом видео автор подробно и наглядно разбирает работу с подзапросам в SQL. 00:00 Подзапросы в SQL (subqueries) 00:52 Запуск подзапросов в SELECT 02:01 Подзапрос, возвращающий список значений 04:25 Подзапросы в UPDATE 05:57 Итоги Смотреть это видео на youtube: youtu.be/Df6tQlWhn3Q
Posted without readable text
LLM'ы в преобразовании запроса на естественном языке в SQL (text2sql) Одной из главных проблем, с которыми сталкиваются компании, это непосредственная работа с базами данных с помощью языка SQL. Поэтому на рынке появляются инструменты, позволяющие писать запрос на естественном языке и получать ответ на языке запросов. В этой статье автор познакомит вас с двумя AI-инструментами для генерации SQL-запросов: SQLCoder De…
MinIO прекратил активную разработку: патчи безопасности рассматриваются по индивидуальным запросам, обновления не тестируются. Для компаний с петабайтами данных в MinIO встает вопрос о миграции. Главная сложность миграции — не выбор нового хранилища, а перенос без остановки бизнес-процессов. Большинство open-source инструментов требуют простоя: приложения нужно останавливать на время переноса данных, а на многотераба…
Основные команды SQL, которые должен знать каждый программист В этой статье автор рассмотрит основные команды SQL, включая агрегатные функции и вложенные подзапросы, на примере работы с MySQL. Базы данных
⚡️ Почему аналитики данных так востребованы и как стать аналитиком в 2026 году? Большинство новичков совершают одну и ту же ошибку: учат всё подряд. SQL, Python, Power BI, статистика… Но работодатели оценивают кандидатов не только по базовым навыкам, но и по другим критериям. Из-за этого многие месяцами рассылают резюме и получают только отказы или полное игнорирование. Андрон Алексанян - аналитик с опытом 9 лет и …
Книга: «Антипаттерны SQL. Как избежать ловушек при работе с базами данных» Язык SQL необходим для работы со структурированными данными. Программисты, прекрасно знающие свой любимый язык (Java, Python или Go), не могут разбираться во всем, и часто не являются экспертами в SQL. Это приводит к появлению антипаттернов — решений, которые на первый взгляд кажутся правильными, но со временем создают все больше проблем. Ба…
Posted without readable text
Базовые SELECT запросы в SQL В этом видеокурсе автор разбирает основы SQL: вы узнаете что такое SQL, научитесь писать SQL-запросы различной сложности. Все эти знания будут легко применимы не только к PostgreSQL, но и к другим СУБД: MySQL, Microsoft SQL Server, Oracle. 0:00:00 Полная выборка данных с SELECT 0:07:06 Выборка и простая арифметика в SQL 0:10:30 Использование DISTINCT 0:15:29 Использование COUNT 0:25…
PostgreSQL: архитектура и тюнинг SQL-запросов Погрузись в архитектуру и прокачай оптимизацию запросов одной из самых популярных open source СУБД – PostgreSQL. 🌐 В программе курса: 🤩 Разберём, как работают СУБД вообще и PostgreSQL в частности: что такое MVCC, ACID, WAL, LRU, PPC/TPC и другие фундаментальные понятия архитектуры баз данных 🤩 Получишь теорию и практику EXPLAIN и EXPLAIN ANALYZE на разных типа запросо…
Оператор SQL IN на понятных примерах В этой статье автор подробно разбирает синтаксис оператора фильтрации SQL IN и рассматривает его использование на практических примерах. Базы данных
Часто заказчики отказываются от внедрения ИИ-ассистентов из-за «грязных» входных данных: PDF с таблицами или сканы плохо индексируются, нейросеть галлюцинирует 🤯 А что, если был бы ИТ-продукт, который не просто распознает символы, а сохраняет логику документа, превращая его в готовый формат для RAG (Markdown/JSON)❔ Это позволило бы клиентам в разы быстрее выводить ИИ-продукты в эксплуатацию и закрыть вопрос импортоз…
Showing the 12 most recent of 45 posts we hold for @databases_secrets. 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.
Citation-graph rank — 309,049 of 1,585,237entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 3 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Базы данных | Access, SQL, Big Data” (@databases_secrets), 30,120 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/databases_secrets.
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.