DEV Community: Elshod Ibodullayev

IELTS 7.5 until step-by-step

Elshod Ibodullayev — Sat, 25 Oct 2025 18:57:10 +0000

📚 Find your books:
☐ Murphy Blue - tabletda qo'ying
☐ Vocabulary in Use - yoniga
☐ Cambridge book - qaysi raqam? (10/11/12/13/14/15?)
☐ Basic IELTS Listening - audio bilan
☐ Maximiser Speaking - ready
☐ ELS Reading - ready

📓 Notebooks prepare:
☐ Notebook 1: Grammar (Murphy)
☐ Notebook 2: Vocabulary (daily words)
☐ Notebook 3: Reading Vocab (from passages)
☐ Notebook 4: Progress Tracking

💻 Kompyuter setup:
☐ Cambridge audio files check (CD yoki download)
☐ Browser bookmarks:

ieltsliz.com
ielts-simon.com
quizlet.com ☐ Voice recorder test (telefonda)


---

**10:30-11:30 (1h) - Murphy Blue Unit 1**

**Birinchi marta properly o'rganamiz:**

Unit 1: Present Simple (I do/work/like etc.)

10:30-10:40 (10 min): Theory o'qish

Left page: grammar explanation
Examples study
Tushunmagan so'zlar? Google translate

10:40-11:10 (30 min): Exercises

Right page: ALL exercises (20+ ta)
Notebook ga yozish
Answers check (kitob oxirida keys bor)
Xatolarni mark qiling

11:10-11:30 (20 min): Practice

10 ta o'z jumlangiz yozish
Present Simple bilan
Notebook ga


---

**11:30-12:00 (30 min) - First Vocabulary**

**Vocabulary in Use:**

Unit 1 (qaysi topic bo'lsa ham):

O'qish: 10 min
10-15 ta muhim so'zni tanlash
Har biri uchun: ✍️ Inglizcha definition ✍️ 1 ta example sentence ✍️ Notebook ga yozish

Goal: Sistema bilan ishlashni o'rganish


---

**12:00-15:00 - LUNCH + REST** 🍽️

---

**15:00-17:00 - PASSIVE LEARNING (Enjoy!)**

**English Series/Movie:**
- Friends yoki TED Talks
- English subtitles
- Relax!

---

**17:00-19:00 - FREE TIME** 🎮

---

**19:00-20:30 - DUSHANBA PREPARATION**

**19:00-19:30 (30 min) - Workspace Final Setup:**

Stol/Table organize:
☐ All books in order
☐ Notebooks stacked
☐ Pens ready
☐ Water bottle
☐ Lighting yaxshi
☐ Quiet space
☐ Telefon silent mode ga o'rgatish (study time)


**19:30-20:00 (30 min) - Cambridge Check:**

Cambridge book ochish:

Qaysi raqam? (10/11/12/13/14/15?)
Test 1 ni topish
Reading Passage 1 ni ko'rish
Listening audio files check
Ertaga shu kitobdan boshlaysiz!


**20:00-20:30 (30 min) - Dushanba Plan Review:**

Bu chatdan Dushanba planini qayta o'qish:

Morning: Grammar, Vocabulary, Reading
Evening: Listening, Writing, Speaking
Mentally prepare
"Tomorrow I start!" 💪


---

**20:30-23:00 - FREE TIME + EARLY SLEEP** 😴

---

## 📅 **YANGILANGAN DUSHANBA PLAN (Sizning materiallar bilan)**

### **07:30-12:30 - ERTALAB**

#### **08:00-09:30 - GRAMMAR (Murphy Blue)**

08:00-08:15: Unit 1 review (15 min)
08:15-08:40: Unit 2 - Present Continuous (25 min)
08:40-09:05: Unit 3 - Present Simple vs Continuous (25 min)
09:05-09:30: Unit 4 - Present Perfect (25 min)

Total: 4 units, 40+ exercises
Notebook ga yozish!


---

#### **09:45-11:15 - VOCABULARY (Vocab in Use)**

09:45-10:30: 2 ta unit from Vocab in Use (45 min)

Har bir unit: 15-20 so'z
Total: 40 so'z
Definitions, examples, notebook

10:30-11:00: Sentences writing (30 min)

40 ta jumla (har bir so'z uchun)

11:00-11:15: Quizlet flashcards create (15 min)

40 ta so'zni app ga kiritish


---

#### **11:30-13:00 - READING**

Option 1: Cambridge (if you have 10-15)

Test 1, Passage 1
20 min: Read + answer
20 min: Check answers
30 min: Vocabulary extraction (25 words)
20 min: Second read

Option 2: ELS Reading (if Cambridge keyinroq)

1 ta passage
Same process


---

### **18:30-23:00 - KECHQURUN**

#### **18:30-19:30 - LISTENING**

18:30-18:45: Basic IELTS Listening - Unit 1 (15 min)

18:45-19:15: Cambridge Listening (if audio bor)

Test 1, Section 1-2 (30 min audio + answers)

19:15-19:30: Analysis (15 min)

Transcript check
Mistakes review


---

#### **20:00-21:00 - WRITING**

20:00-20:20: IELTS Liz website

1 ta Task 1 model essay o'qish
Structure analyze
ieltsliz.com/ielts-writing-task-1

20:20-20:40: Useful phrases

10 ta phrase yozib olish
"The graph shows..."
"There was a significant increase..."

20:40-21:00: Practice

1 ta paragraph yozish (50-70 words)
Introduction yoki overview


---

#### **21:15-22:15 - SPEAKING (Maximiser Speaking)**

21:15-21:45: Part 1 practice (30 min)

Maximiser dan 10 ta Part 1 questions
Telefonga yozish
Topics: Work, Study, Hometown

21:45-22:15: Review (30 min)

Recording eshitish
Mistakes yozish
Vocabulary gaps identify


---

#### **22:15-23:00 - REVIEW**

Grammar xatolarni qayta (15 min)
Vocabulary flashcards - Quizlet (20 min)
Progress tracking (10 min)


---

## 🎯 **MATERIAL PRIORITIES**

### **Har kuni ishlatadigan kitoblar:**

**DUSHANBA-JUMA:**
1. **Murphy Blue** - every morning (grammar foundation)
2. **Vocabulary in Use** - every morning (systematic vocab)
3. **Cambridge** - every morning (reading) + every evening (listening)
4. **Basic IELTS Listening** - every evening (listening skills)
5. **Maximiser Speaking** - every evening (speaking practice)

**ELS Reading:**
- Extra practice uchun (agar vaqt bo'lsa)
- Yoki Cambridge tugagandan keyin
- Yoki Reading da extra drill kerak bo'lsa

---

### **Materials Usage Priority:**

**PHASE 1 (Month 1-2): FOUNDATION**

PRIMARY:
✅ Murphy Blue (full book)
✅ Vocabulary in Use (2 units/day)
✅ Cambridge Test 1-4 (agar 10-15 bor bo'lsa)
✅ Basic IELTS Listening (systematic)

SECONDARY:
✅ Maximiser Speaking (for speaking practice)
✅ ELS Reading (if need extra)


**PHASE 2 (Month 3-4): DEVELOPMENT**

PRIMARY:
✅ Cambridge Test 5-8
✅ Advanced Vocabulary practice
✅ Maximiser Speaking (intensive)

SECONDARY:
✅ Murphy Red (if needed - advanced grammar)
✅ ELS Reading (speed practice)

Async Await Delay

Elshod Ibodullayev — Tue, 16 Sep 2025 03:00:15 +0000

🔹 1. async va await

async → metodni asinxron qilish uchun yoziladi.

await → kutish, lekin bloklamasdan kutish.

public async Task RunAsync()
{
Console.WriteLine("Boshlanish");
await Task.Delay(2000); // 2 soniya kutadi, lekin boshqa kodlar ishlashi mumkin
Console.WriteLine("Tugadi");
}

🔹 2. Task va Task

Task → “bo‘sh ish” (natija qaytarmaydi).

Task → natija qaytaradigan async metod.

public async Task GetNumberAsync()
{
await Task.Delay(1000); // simulyatsiya
return 42;
}

int result = await GetNumberAsync(); // 42

🔹 3. Task.Delay vs Thread.Sleep

Task.Delay → asinxron kutish. Thread band bo‘lmaydi.

Thread.Sleep → synchronous kutish. Thread bloklanadi.

// Bu UI ni qotiradi
Thread.Sleep(3000);

// Bu UI ni qotirmaydi
await Task.Delay(3000);

🔹 4. Task.Run

Fon ishini alohida oqimda bajaradi.

await Task.Run(() =>
{
// Og‘ir hisob-kitob
Thread.Sleep(2000);
Console.WriteLine("Hisob tugadi");
});

🔹 5. WhenAll va WhenAny

Task.WhenAll – bir nechta vazifani parallel bajaradi va hammasi tugashini kutadi.

Task.WhenAny – birinchi tugagan vazifani kutadi.

var t1 = Task.Delay(2000);
var t2 = Task.Delay(3000);

await Task.WhenAll(t1, t2); // ikkalasini ham kutadi
await Task.WhenAny(t1, t2); // birinchi tugaganini kutadi

🔹 6. ConfigureAwait

Server (ASP.NET Core) yoki UI dasturlarida context switching muhim.

await SomeTask().ConfigureAwait(false);

👉 Bu UI kontekstiga qaytmasdan ishlash uchun kerak (ko‘p server kodlarda ishlatiladi).

🔹 7. CancellationToken

Asinxron vazifani to‘xtatish uchun ishlatiladi.

public async Task RunAsync(CancellationToken token)
{
for (int i = 0; i < 10; i++)
{
token.ThrowIfCancellationRequested();
await Task.Delay(500);
Console.WriteLine(i);
}
}

🔹 8. IAsyncEnumerable (async foreach)

Katta ma’lumot oqimini bosqichma-bosqich olish uchun.

public async IAsyncEnumerable GetNumbersAsync()
{
for (int i = 1; i <= 5; i++)
{
await Task.Delay(500);
yield return i;
}
}

await foreach (var num in GetNumbersAsync())
{
Console.WriteLine(num);
}

🔹 9. Common async API’lar

C# va .NET da tez-tez ishlatiladigan async metodlar:

Task.Delay – vaqtincha kutish

HttpClient.GetAsync – internetdan ma’lumot olish

Stream.ReadAsync / WriteAsync – fayl/stream bilan ishlash

SignalR.SendAsync – real-time xabar jo‘natish

DbContext.SaveChangesAsync – ma’lumotlar bazasiga yozish

📌 Xulosa

Thread.Sleep → bloklaydi, UI qotadi.

Task.Delay → asinxron kutadi, UI qotmaydi.

Task.Run → og‘ir ishni boshqa oqimga o‘tkazadi.

Task.WhenAll / WhenAny → parallel boshqaruv.

CancellationToken → ishni to‘xtatish.

IAsyncEnumerable → oqim bilan ketma-ket natija olish.

i know data

Elshod Ibodullayev — Tue, 16 Sep 2025 02:58:44 +0000

ORM (Object-Relational Mapping) nima va vazifasi?

ORM – bu obyektlar (C# klasslari) bilan ma’lumotlar bazasi jadvallari o‘rtasida bog‘lanish texnologiyasi.

Ya’ni, SQL yozmasdan, C# kod orqali ma’lumotlar bazasiga murojaat qilish imkonini beradi.

Vazifasi:

Kodni soddalashtirish

SQL yozishni kamaytirish

OOP bilan bazani boshqarish

👉 Masalan: User klassingiz bo‘lsa, ORM uni Users jadvali bilan bog‘lab beradi.

Dapper va ADO.NET

ADO.NET

Bu past darajadagi texnologiya.

Siz qo‘lda SQL query yozasiz, SqlConnection, SqlCommand, SqlDataReader ishlatasiz.

Juda tez ishlaydi, lekin ko‘p kod yozish kerak.

Dapper

Bu yengil ORM.

SQL yozishingiz kerak, lekin u natijalarni avtomatik klasslarga map qilib beradi.

Tezligi ADO.NET darajasida, lekin ishlatish qulayroq.

👉 Dapper – ORM va ADO.NET o‘rtasidagi “oraliq” variant.

Entity Framework (EF) nima?

EF – bu Microsoft ORM frameworki.

U orqali SQL yozmasdan, faqat C# klasslari bilan ishlash mumkin.

EF o‘zi query yaratib, bazaga yuboradi.

👉 Masalan:

var users = db.Users.ToList();

Bu kod ostida EF avtomatik SELECT * FROM Users SQL yozib bajaradi.

Code First va CRUD operatsiyalari

Code First

Avval C# da klasslar yaratasiz (User, Product va hokazo).

EF shu klasslardan bazada jadval yaratadi.

Kod → Baza (Code First).

CRUD (asosiy amallar):

Create – qo‘shish (db.Users.Add(...))

Read – o‘qish (db.Users.ToList())

Update – yangilash (db.Users.Update(...))

Delete – o‘chirish (db.Users.Remove(...))

EF Core nima va nima uchun kerak?

Entity Framework Core – EF ning yangi, engil va cross-platform versiyasi.

U Windows, Linux, Mac hamda .NET 5/6/7 bilan ishlaydi.

Qanday kerak?

Tezroq va moslashuvchan

Migration orqali bazani boshqarish

Katta loyihalarda SQL yozishni kamaytirish uchun

DbContext nima?

DbContext – bu EF orqali baza bilan bog‘lanish markazi.

Unda DbSet lar bor.

U orqali siz CRUD operatsiyalarni bajarasiz.

👉 Misol:

public class AppDbContext : DbContext
{
public DbSet Users { get; set; }
}

DbSet nimani bildiradi?

DbSet – bu ma’lumotlar bazasidagi jadvalning modeli.

Masalan, DbSet – bu Users jadvalini bildiradi.

👉 Kod:

db.Users.Add(new User { Name = "Ali" });
db.SaveChanges();

Bu kod INSERT INTO Users (Name) VALUES ('Ali') bajaradi.

LINQ (Language Integrated Query)

LINQ – bu ma’lumotlar bilan ishlash uchun yozilgan C# sintaksisi.

U orqali massivlar, listlar, va bazadagi ma’lumotlar bilan query yozish mumkin.

👉 Misol:

var users = db.Users
.Where(u => u.Age > 18)
.OrderBy(u => u.Name)
.ToList();

Bu SQLda:

SELECT * FROM Users WHERE Age > 18 ORDER BY Name;

✅ Xulosa:

ORM – obyektlar va jadvallarni bog‘laydi.

ADO.NET – qo‘lda SQL yoziladi.

Dapper – tez va yengil ORM.

EF / EF Core – kuchli ORM, SQL yozmasdan ishlash mumkin.

DbContext – baza bilan aloqa nuqtasi.

DbSet – jadval modelini bildiradi.

LINQ – query yozish uchun C# sintaksisi.

Dependency Injection (DI) and Middleware

Elshod Ibodullayev — Thu, 28 Aug 2025 10:10:43 +0000

Dependency Injection (DI) — bu loyihadagi sinflar o‘rtasida qattiq bog‘lanishni kamaytiradigan dizayn pattern.

Oddiy qilib aytsak:

Bir sinf (masalan, Controller) boshqa sinfni o‘zi yaratib olmaydi, balki tashqaridan (ASP.NET Core container) oladi.

Bu sinflarni testlash, almashtirish va sozlashni osonlashtiradi.

Oddiy misol:
Servis interfeysi
public interface IDatabaseService
{
string GetData();
}

Servis implementatsiyasi
public class SqlDatabaseService : IDatabaseService
{
public string GetData() => "SQL Database dan ma'lumot olindi";
}

Servisni ro‘yxatdan o‘tkazish (Program.cs / Startup.cs)
builder.Services.AddTransient();

Controllerda foydalanish

public class HomeController : Controller
{
    private readonly IDatabaseService _databaseService;

    // DI orqali konstruktor orqali keladi
    public HomeController(IDatabaseService databaseService)
    {
        _databaseService = databaseService;
    }

    public IActionResult Index()
    {
        var data = _databaseService.GetData();
        return Content(data);
    }
}

➡️ Bunda HomeController qaysi servis ishlatilishini bilmaydi – DI container unga to‘g‘risini beradi.
Agar keyinroq PostgreSqlDatabaseService yozilsa, faqatgina DI ro‘yxatida almashtirish kifoya. Controller kodi o‘zgarmaydi.

Middleware

ASP.NET Core’da har bir so‘rov va javob pipeline orqali o‘tadi.
Pipeline — bu Middleware’lar zanjiri. Har bir middleware:

So‘rovni qabul qiladi.

O‘z vazifasini bajaradi (masalan, loglash, autentifikatsiya, exception handling).

Keyingi middleware’ga uzatadi (await _next(context) orqali).

Oddiy Middleware

public class LoggingMiddleware
{
    private readonly RequestDelegate _next;

    public LoggingMiddleware(RequestDelegate next)
    {
        _next = next;
    }

    public async Task InvokeAsync(HttpContext context)
    {
        Console.WriteLine($"So'rov keldi: {context.Request.Path} | {DateTime.Now}");

        await _next(context); // Keyingi middlewarega o'tadi

        Console.WriteLine($"So'rov tugadi: {DateTime.Now}");
    }
}

Middleware’ni ulash
var app = builder.Build();

app.UseMiddleware<LoggingMiddleware>(); // Custom middleware
app.UseAuthentication();                // Ichki middleware
app.UseAuthorization();

app.MapControllers();

⚡ Muhim: Middleware’lar tartibi juda muhim. Masalan:

UseAuthentication() Always UseAuthorization() dan oldin turishi kerak.

Exception handling middleware (UseExceptionHandler) boshida turadi.

Umumlashtirib aytganda

AppSettings → konfiguratsiya fayllari (umumiy va muhitga xos).

Dependency Injection → komponentlarni bir-biridan mustaqil qilish.

Middleware → so‘rov va javob jarayonida ishlovchi zanjir.

AppSettings.json va AppSettings.Development.json

Elshod Ibodullayev — Thu, 28 Aug 2025 10:08:58 +0000

ASP.NET Core’da konfiguratsiya (sozlamalar) appsettings.json fayli orqali saqlanadi.
Bu fayllar json formatida bo‘lib, unda ConnectionString, Logging, API sozlamalari, Custom Settings kabi umumiy parametrlar saqlanadi.

Asosiy fayl: appsettings.json

Loyihaning barcha muhitlarida umumiy ishlatiladi (Development, Staging, Production).

Masalan, asosiy ulanish satri yoki loglash darajasi.

{
  "ConnectionStrings": {
    "DefaultConnection": "Server=ProdServer;Database=ProdDB;User=sa;Password=123;"
  },
  "Logging": {
    "LogLevel": {
      "Default": "Information"
    }
  }
}

Muhitga xos fayl: appsettings.Development.json

Bu fayl faqat Development (dasturchilar muhitida) ishlatiladi.

Unda ishlab chiqish uchun qulayroq sozlamalar yoziladi. Masalan, LocalDB ulanishi yoki loglarni batafsilroq chiqarish.

{
  "ConnectionStrings": {
    "DefaultConnection": "Server=(localdb)\\mssqllocaldb;Database=DevDB;Trusted_Connection=True;"
  },
  "Logging": {
    "LogLevel": {
      "Default": "Debug",
      "Microsoft": "Warning"
    }
  }
}

⚡ Muhitni aniqlash: ASP.NET Core avtomatik ravishda ASPNETCORE_ENVIRONMENT o‘zgaruvchisiga qarab to‘g‘ri faylni yuklaydi:

Development → appsettings.Development.json

Staging → appsettings.Staging.json

Production → appsettings.Production.json

👉 Bu orqali bir xil kodni turli muhitlarda sozlamalarni o‘zgartirmasdan ishlatish mumkin.

ASP.NET Core va .NET Framework

Elshod Ibodullayev — Wed, 27 Aug 2025 19:53:39 +0000

ASP.NET Core MVC asosiy konseptlarini tushuntirib boraman. Har bir mavzu alohida tahlil qilinadi.

ASP.NET Core va .NET Framework Farqi
ASP.NET Core yangi avlod, ochiq manba kodli va ko'p platformali framework simplilearn.com
Windows, macOS va Linux operatsion sistemalarda ishlaydi
Yuqori ishlash tezligiga ega
Bulutga moslashtirilgan arxitektura
.NET Framework faqat Windowsda ishlaydi

🔹 Controller nima?

Controller — bu ko‘prik.

U foydalanuvchi yuborgan so‘rovni (request) qabul qiladi.

Keyin kerak bo‘lsa modeldan ma’lumot oladi yoki saqlaydi.

Oxirida foydalanuvchiga natija (view yoki json, text, file va h.k.) qaytaradi.

👉 Oddiy qilib aytganda: Controller = “Foydalanuvchi bilan dastur o‘rtasidagi vositachi”.

🔹 Action nima?

Action — bu Controller ichidagi funksiya/metod, ya’ni aniq bir vazifani bajaruvchi qism.

Har bir Action odatda:

URL orqali chaqiriladi (masalan, /Home/Index yoki /Home/GetData).

O‘ziga xos natija qaytaradi (masalan, web sahifa, json, text, file va boshqalar).

🔹 Misol orqali

public class HomeController : Controller
{
    // 1) Oddiy Action: Sahifa ko'rsatadi
    public IActionResult Index()
    {
        return View(); // Index.cshtml faylini qaytaradi
    }

    // 2) Ma'lumot olish Action: JSON qaytaradi
    [HttpGet]
    public JsonResult GetData()
    {
        var data = new { Name = "Ali", Age = 25 };
        return Json(data);
    }

    // 3) Yangi ma'lumot yuborish Action
    [HttpPost]
    public IActionResult SaveData(string name, int age)
    {
        // kelgan ma'lumotni saqlash
        return Ok("Ma'lumot saqlandi!");
    }
}

👉 Bu yerda:

HomeController → Controller (ko‘prik).

Index, GetData, SaveData → Action’lar (aniq vazifalarni bajaradi).

🔹 Hayotiy o‘xshatish

Controller → Restorandagi ofitsiant (buyurtmani qabul qiladi va oshxonaga yetkazadi).

Action → Ofitsiantning bajaradigan harakati:

Buyurtmani olish

Ovqatni olib kelish

Hisobni chiqarish

Xunit testlar

Elshod Ibodullayev — Wed, 27 Aug 2025 19:18:44 +0000

[Fact] oddiy holarlarda yani xilma xillik bulmaganda testimis tuslanmasa biz bergan malumotni tuslamaydi yani usha bergan malimotni qaytarib olamiz
[theory]
[Inline[Data(null)] null qiymat
[Inline[Data("")] string
[Inline[Data(" ")] bush joy yani space
qiymat berib yubormoqchi bulsak theory ekan

ASP.NET Core da MIDDLEWARE

Elshod Ibodullayev — Mon, 25 Aug 2025 05:09:11 +0000

Middleware deb Sql Surovni yoki javobni handle qiladigan code ga aytiladi
xar qanday Middleware kampanintini anbiq bir maqsadi buladi authenticaction, Static Files, logging, shunga uxshash va boshqalar
serverga kelgan http surovni request pipiline orqali chaqiruvchi Middleware Companentlar handle qiladi

ASP.NET Core’da Logging: ILogger, ILogger va Serilog To‘liq Tushuntirish

Elshod Ibodullayev — Sun, 24 Aug 2025 11:33:32 +0000

Logging — To‘liq Tushunish

Logging nima va nima uchun kerak?
Logging — bu dastur ichida sodir bo‘layotgan hodisa va voqealarni yozib borish jarayoni.
Uning asosiy maqsadi:

✅ Xatoliklarni aniqlash (buglarni tezroq topish)
✅ Jarayonlarni kuzatish (masalan, foydalanuvchi qaysi API’ni chaqirdi)
✅ Monitoring va audit qilish (kattaroq loyihalarda majburiy)
✅ Tahlil qilish (dastur samaradorligi, ishlash vaqti, resurs sarfi)

logging nima => output window yani bu rasmdagi joy

bu ham logging

LINQ (Language Integrated Query)

Elshod Ibodullayev — Fri, 22 Aug 2025 05:28:00 +0000

LINQ (Language Integrated Query) To‘liq Tushuntirish

LINQ (Language Integrated Query) — bu .NET tilida (C#, VB.NET va F#) ma’lumotlarni so‘roqlash (query qilish) imkonini beradigan texnologiya. U ma’lumotlarni turli manbalardan (kolektsiyalar, massivlar, ma’lumotlar bazasi, XML, JSON va boshqalar) o‘qish va ular ustida amallar bajarishni soddalashtiradi.

LINQ dasturchiga SQLga o‘xshash query sintaksisi yoki method chaining usulida yozish imkonini beradi. Bu esa kodni qisqa, tushunarli va qo‘llab-quvvatlashni oson qiladi.

LINQ ning Afzalliklari

Kod qisqaligi – ko‘p qatorli foreach sikllarni bir qator LINQ ifodasi bilan almashtirish mumkin.
O‘qilishi oson – SQLga o‘xshash sintaksis orqali ma’lumotlar ustida ishlash soddalashadi.
Universal – har xil turdagi ma’lumot manbalariga (memorydagi koleksiya, DB, XML, JSON) ishlaydi.
Type safety – kompilyator xatolarni oldindan aniqlaydi.
Deferred execution – query natijasi faqat ishlatilganda bajariladi (optimallashtirish imkoniyati).

LINQ Sintaksislari

LINQ ikki xil yozilishi mumkin:

1. Query Sintaksis (SQLga o‘xshash)

var result = from user in users
             where user.Age > 18
             orderby user.Name
             select user;

2. Method Sintaksis (Lambda ifodalar bilan)

var result = users
    .Where(u => u.Age > 18)
    .OrderBy(u => u.Name)
    .Select(u => u);

Ikkalasi ham bir xil natija beradi, faqat yozilish uslubi boshqacha.

LINQ Qayerlarda Ishlatiladi?

LINQ asosan quyidagi sohalarda qo‘llaniladi:

Kolleksiyalar bilan ishlash

Massiv yoki List ichidagi elementlarni filter qilish, tartiblash, guruhlash.

   int[] numbers = { 1, 2, 3, 4, 5, 6 };
   var evenNumbers = numbers.Where(n => n % 2 == 0);

Entity Framework va DB bilan ishlash

SQL yozmasdan, C# kodida query yozish.

   var students = context.Students
                         .Where(s => s.Age > 18)
                         .OrderBy(s => s.Name)
                         .ToList();

XML bilan ishlash

   XDocument doc = XDocument.Load("students.xml");
   var names = from s in doc.Descendants("student")
               where (int)s.Element("age") > 18
               select s.Element("name").Value;

JSON bilan ishlash (Newtonsoft yoki System.Text.Json orqali LINQ-to-JSON)

   JObject json = JObject.Parse(jsonString);
   var names = json["students"]
                 .Where(s => (int)s["age"] > 18)
                 .Select(s => s["name"]);

Parallel ishlash (PLINQ)

Katta hajmdagi ma’lumotlarni tezroq qayta ishlash uchun.

   var primes = numbers.AsParallel()
                       .Where(n => IsPrime(n));

LINQ Operatorlari

LINQ’da ko‘plab operatorlar mavjud. Ularni guruhlarga bo‘lish mumkin:

1. Filtering (Filtrlash)

Where – shartga mos elementlarni olish
OfType – ma’lum tipdagi elementlarni olish

2. Projection (Transformatsiya)

Select – elementlarni boshqa shaklga o‘zgartirish
SelectMany – nested kolleksiyalarni yoyib yuborish

3. Sorting (Tartiblash)

OrderBy, OrderByDescending
ThenBy, ThenByDescending

4. Grouping (Guruhlash)

GroupBy

5. Joining (Bog‘lash)

Join – ikki kolleksiyani bog‘lash
GroupJoin – grouped join

6. Aggregation (Hisoblash)

Count, Sum, Average, Min, Max

7. Quantifiers (Shartlar tekshirish)

Any, All, Contains

8. Element Operators

First, FirstOrDefault
Single, SingleOrDefault
ElementAt

9. Set Operators

Distinct
Union
Intersect
Except

10. Conversion

ToList, ToArray, ToDictionary

Amaliy Misollar

1. Oddiy Filter va Select

var adults = users.Where(u => u.Age >= 18)
                  .Select(u => new { u.Name, u.Age });

2. Guruhlash

var groupedByCity = users.GroupBy(u => u.City);

3. Join

var query = from student in students
            join grade in grades on student.Id equals grade.StudentId
            select new { student.Name, grade.Mark };

4. Aggregation

var avgAge = users.Average(u => u.Age);

LINQ Qanday Muammolarni Yechadi?

Kodning uzunligi va murakkabligi – foreach va if kombinatsiyalarini soddalashtiradi.
SQL va C# o‘rtasidagi tafovut – kod ichida SQL yozishga hojat yo‘q.
Ma’lumot manbalari turli xil bo‘lsa – LINQ bir xil sintaksis bilan ishlaydi.
Parallel ishlash – katta hajmdagi ma’lumotlarni tezroq qayta ishlash.

Xulosa

LINQ — bu .NET ekotizimidagi juda kuchli vosita bo‘lib, ma’lumotlar bilan ishlash jarayonini sezilarli darajada yengillashtiradi. Dasturchilar uchun:

Kolleksiya ustida ishlash
Ma’lumotlar bazasiga so‘rovlar
XML/JSON bilan ishlash
Parallel hisoblash

kabi vazifalarda eng qulay va samarali yondashuvlardan biridir.

✍️ Ushbu maqolani dev.to saytida joylashtirib, amaliy misollarni kengaytirish orqali yangi boshlovchilar va professional dasturchilar uchun LINQ haqida mukammal qo‘llanma qilish mumkin.

SQL,PostgreSQL, Database RDBMS, Sql NoSql farqi

Elshod Ibodullayev — Wed, 20 Aug 2025 17:00:29 +0000

Database nima?

Database (ma’lumotlar bazasi) — bu ma’lumotlarni saqlash, boshqarish va qayta ishlash uchun joy.

Masalan, telefoningizdagi kontaktlar ro‘yxati ham kichik ma’lumotlar bazasi.

Internet-do‘kon saytida esa foydalanuvchilar, buyurtmalar, mahsulotlar — hammasi ma’lumotlar bazasida saqlanadi.

👉 Demak, database = katta elektron daftar.

RDBMS nima? RDBMS (Relational Database Management System) — bu relatsion ma’lumotlar bazasi boshqaruv tizimi.

Relatsion degani = ma’lumotlar jadval (table) ko‘rinishida saqlanadi.

Har bir jadvalda qator (row) va ustun (column) bo‘ladi.

Id	Name	Age
1	Ali	20
2	Dilnoz	22

RDBMS misollari: SQL Server, PostgreSQL, MySQL, Oracle.

3. SQL va NoSQL farqi

SQL (RDBMS)

Jadval ko‘rinishida (rows, columns) saqlanadi.
Qattiq struktura (schema) bo‘ladi.
Kuchli JOIN va transaction qo‘llab-quvvatlaydi.
Misollar: SQL Server, PostgreSQL, MySQL.

NoSQL

Jadval emas, balki hujjat, kalit-qiymat, grafik kabi formatlarda saqlaydi.
Qattiq schema yo‘q → moslashuvchan.
Juda katta hajmdagi ma’lumotlarda (Big Data) yaxshi ishlaydi.
Misollar: MongoDB (document), Redis (key-value).

👉 Esda qolarli:

SQL = an’anaviy daftar (qatordan-ustunlardan iborat)
NoSQL = shaxsiy daftar (kim qanday yozsa, shunday turadi)

Xususiyat	SQL (RDBMS)	NoSQL
Ma’lumot formati	Jadval (rows va columns)	Hujjat, kalit-qiymat, grafik, columnar
Schema	Qattiq (oldindan belgilangan)	Moslashuvchan (schema-less)
Moslik	Murakkab JOIN va transaction’lar	Katta hajm, tezkor va kengayuvchan
Kengayish	Vertical scaling (serverni kuchaytirish)	Horizontal scaling (ko‘p server qo‘shish)
Qo‘llanish sohasi	An’anaviy ilovalar, moliya, ERP, CRM	Big Data, real-time analytics, IoT
Misollar	SQL Server, PostgreSQL, MySQL, Oracle	MongoDB, Redis, Cassandra, Neo4j

4. SQL Server va PostgreSQL

SQL Server → Microsoft ishlab chiqqan kuchli RDBMS. Korporativ loyihalarda keng qo‘llanadi.

PostgreSQL → Ochiq manbali (open-source) RDBMS. Juda kuchli va moslashuvchan.

Har ikkalasi ham SQL tilida ishlaydi, lekin sintaksisda ozgina farqlar bo‘lishi mumkin.

👉 Esda qolsin:

SQL Server = pullik, Microsoft ekotizimida

PostgreSQL = bepul, kuchli open-source

5. SQL asosiy komandalar

SELECT * FROM Users;
👉 Users jadvalidagi barcha ma’lumotlarni olib keladi.
INSERT — yangi ma’lumot qo‘shish
INSERT INTO Users (Name, Age)
VALUES ('Ali', 20);
👉 Users jadvaliga yangi foydalanuvchi qo‘shadi.
UPDATE — ma’lumotni yangilash
UPDATE Users
SET Age = 25
WHERE Name = 'Ali';


👉 Ali ismli foydalanuvchining yoshini 25 ga o‘zgartiradi.
DELETE — ma’lumotni o‘chirish
DELETE FROM Users
WHERE Name = 'Ali';


👉 Ali ismli foydalanuvchini o‘chiradi.
Primary Key va Foreign Key
Primary Key

Jadvaldagi har bir qatorni unikal aniqlab beradi.

Masalan, Users jadvalidagi Id ustuni.

Takrorlanmaydi va bo‘sh bo‘lmaydi.

CREATE TABLE Users (
    Id INT PRIMARY KEY,
    Name NVARCHAR(50),
    Age INT
);
Foreign Key

Bir jadvaldagi ustun boshqa jadvaldagi primary key ga ulanadi.

Jadval o‘rtasida bog‘lanish yaratadi.

CREATE TABLE Orders (
    OrderId INT PRIMARY KEY,
    UserId INT,
    FOREIGN KEY (UserId) REFERENCES Users(Id)
);


👉 Bu yerda Orders.UserId → Users.Id ga ulanadi.
NULL qiymat

NULL = qiymat yo‘qligi (bo‘sh, noma’lum).

Bu 0 emas, bo‘sh string emas.

Masalan:

Age = NULL → yosh kiritilmagan.

NULL bilan ishlash
SELECT * FROM Users WHERE Age IS NULL;


👉 Yoshi kiritilmagan foydalanuvchilarni chiqaradi.

SELECT * FROM Users WHERE Age IS NOT NULL;

JOIN turlari JOIN — bu ikki yoki undan ortiq jadvallarni bog‘lab, ma’lumotni birlashtirish. 🔹 INNER JOIN Faqat ikkala jadvalda ham mos keladigan yozuvlarni qaytaradi.

SELECT u.Name, o.OrderId
FROM Users u
INNER JOIN Orders o ON u.Id = o.UserId;

👉 Faqat buyurtma qilgan foydalanuvchilar chiqadi.

🔹 LEFT JOIN

Chap jadvaldagi hamma yozuvlar chiqadi, o‘ng jadvalda mos kelmasa → NULL.

SELECT u.Name, o.OrderId
FROM Users u
LEFT JOIN Orders o ON u.Id = o.UserId;

👉 Hamma foydalanuvchilar chiqadi, buyurtmasi bo‘lmasa NULL.

🔹 RIGHT JOIN

O‘ng jadvaldagi hamma yozuvlar chiqadi, chap jadvalda mos kelmasa → NULL.

SELECT u.Name, o.OrderId
FROM Users u
RIGHT JOIN Orders o ON u.Id = o.UserId;

👉 Hamma buyurtmalar chiqadi, foydalanuvchisi yo‘q bo‘lsa NULL.

🔹 FULL OUTER JOIN

Ikkala jadvaldan hamma yozuvlarni qaytaradi, mos kelmasa → NULL.

SELECT u.Name, o.OrderId
FROM Users u
FULL OUTER JOIN Orders o ON u.Id = o.UserId;

👉 Hamma foydalanuvchilar va hamma buyurtmalar chiqadi.

WHERE va HAVING farqi

WHERE → qatorlarni guruhlashdan oldin filtrlash uchun.

HAVING → GROUP BY’dan keyin filtr qilish uchun.

-- WHERE bilan (oddiy filtr)
SELECT * FROM Users
WHERE Age > 18;

-- HAVING bilan (agregat filtr)
SELECT Age, COUNT(*) AS CountUsers
FROM Users
GROUP BY Age
HAVING COUNT(*) > 2;

👉 Esda qolsin:
WHERE = oddiy shart
HAVING = guruhlangan natijaga shart

GROUP BY va ORDER BY GROUP BY Qatorlarni guruhlaydi va agregat funksiyalar bilan ishlaydi.

SELECT Age, COUNT(*) AS CountUsers
FROM Users
GROUP BY Age;

👉 Har bir yosh nechta borligini ko‘rsatadi.
ORDER BY
Natijani saralaydi.

// kamayish buyicha tartiblash
SELECT * FROM Users
ORDER BY Age DESC;
//usish buyicha tartiblash
SELECT * FROM Users
ORDER BY Age ASC;

👉 Yosh bo‘yicha kamayish tartibida chiqaradi.

Index nima?

Index — bu ma’lumotni tezroq topish uchun maxsus tuzilma (xuddi kitobdagi “alfavit bo‘yicha ko‘rsatkich” kabi).

Foydasi: SELECT tezlashadi.

Kamchiligi: INSERT/UPDATE/DELETE sekinlashishi mumkin (chunki index ham yangilanadi).

CREATE INDEX idx_users_name ON Users(Name);

👉 Endi WHERE Name = 'Ali' so‘rovi juda tez ishlaydi.

Simple SELECT + Filtering

SELECT Name, Age
FROM Users
WHERE Age > 18 AND Name LIKE 'A%';
// qaysidur  ism ni olmoqchi bulsa '_' shunaqa belgi orqali topamiz

👉 Bu yerda:

Faqat Age > 18 bo‘lgan foydalanuvchilar

Ismi A harfi bilan boshlanuvchilar chiqadi

📌 Xulosa

JOIN → jadvallarni bog‘laydi (INNER, LEFT, RIGHT, FULL).
WHERE → oddiy filtr, HAVING → guruhlangan natijaga filtr.
GROUP BY → ma’lumotni guruhlash, ORDER BY → saralash.
Index → tez qidirish uchun “kitobdagi ko‘rsatkich” kabi.
SELECT + WHERE → kerakli ma’lumotni tanlab olish.

Rasmlar C# dasturlashga oid

Elshod Ibodullayev — Wed, 20 Aug 2025 16:31:54 +0000