Channel
@Sql_codings
On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
3,804subscribers
-6 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001333382708 |
|---|---|
| Type | Channel |
| Username | @Sql_codings |
| Created | Between 1 March 2018 and 13 April 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Sql_codings |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 17 Sept 2026, 04:41 | 3,804 | -2 |
| 9 Sept 2026, 18:36 | 3,806 | -5 |
| 4 Sept 2026, 07:39 | 3,811 | +1 |
| 31 Aug 2026, 14:45 | 3,810 | no change |
| 31 Aug 2026, 14:30 | 3,810 | first reading |
20 posts held, back to 13 April 2020 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
207 reactions across 19 posts, in 4 distinct kinds. The most used accounts for 86.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 178 | 86.0% | |
| 🤔 | 18 | 8.70% | |
| 👏 | 6 | 2.90% | |
| 👎 | 5 | 2.42% |
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 20 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 207 reactions 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 13 April 2020 to 9 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.
Question: Given this data: id | date | x 1 | 2026-01-01 | 10 1 | 2026-01-05 | 20 1 | 2026-01-10 | 30 1 | 2026-01-15 | 40 1 | 2026-01-20 | 50 2 | 2026-01-02 | 100 2 | 2026-01-06 | 200 2 | 2026-01-11 | 300 2 | 2026-01-16 | 400 2 | 2026-01-21 | 500 Question: For each id, return the latest 3 dates and their corresponding x values as separate columns. Expected output: id | x_1 | x_2 | x_3 1 | 50 | 40 | 3…
🤔1
When assigning unique identifiers to rows based on a specified order, three key functions come into play: ROW_NUMBER, RANK, and DENSE_RANK. Consider the following table: | Name | Score | |-------- |-------| | Alice | 90 | | Bob | 90 | | Carol | 85 | | David | 78 | ROW_NUMBER: The simplest of the three, ROW_NUMBER assigns a unique number to each row based on the specified order. Ea…
👍13🤔2
Here's a snippet of code written in C: for(int i=0;i<n;i++) { for(int j=0;j<n;j++) { //some operation } } How can I write something equivalent in SQL? Solution:Alias say, you are asked to count the frequency of each color occurring in the same table , so you can write something like this: select distinct color ,(select count(*) from colors where c.color=color) from colors c;
👍71🤔12👏3
https://dataengineeringacademy.medium.com/5-sql-queries-every-data-engineer-scientist-should-know-d68261167f1a
👍11
File, posted without a caption
👍6
File, posted without a caption
👍5
https://towardsdatascience.com/mysql-vs-postgresql-3d48891452a
👍4
https://play.google.com/store/apps/details?id=com.sololearn.sql If you are starting with SQL and wish to code the queries as you learn more about SQL , Sololearn is perfect place for you.
👍6
https://www.udemy.com/course/the-complete-sql-course-2020-become-a-mysql-master/?couponCode=SQLCOURSE29 Get this course for free. Just two days before it expires.
👍5
Photo, posted without a caption
👍6
You are given this database, your task is to output➡
👍5
Write a sql query to find the Joining date of Employee in YYYY-DAY-Date format.
👍6
Showing the 12 most recent of 20 posts we hold for @Sql_codings. 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“SQL Learning 💻” (@Sql_codings), 3,804 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Sql_codings.
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.