Biznes-tizimlar uchun ma’lumotlar modeli
Menejer mahsulot narxini 15 000 dan 16 500 so‘mga o‘zgartirdi. O‘tgan oyda chiqarilgan hisob-fakturalardagi summa ham o‘zgarib qolishi kerakmi?
Javobingizni jadval tuzilishi nuqtai nazaridan o‘ylang: narx qayerda saqlanadi?
order_items da faqat product_id bo‘lsa va narx doim products dan olinsa, eski hisob-faktura qanday ko‘rinadi?Bu ma’ruza oxirida siz quyidagilarni bajara olasiz...
$fillable, casts(), bog‘lanishlar, scope larMa’lumotnomalar, hujjatlar va registrlar
Ma’lumotnoma, hujjat, registr
| Tur | OmborPro jadvallari | Xususiyati | O‘zgarishi |
|---|---|---|---|
| Ma’lumotnoma | products, categories, warehouses, counterparties, users | Barqaror obyektlar, boshqalar ularga murojaat qiladi | Tahrirlanadi, soft delete |
| Davriy ma’lumotnoma | exchange_rates | Sana bo‘yicha qiymat | Kuniga bitta yozuv |
| Hujjat | orders + order_items, invoices, payments | Raqam, sana, holat, qatorlar, summa | O‘tkazilgach — o‘zgarmaydi |
| Registr / jurnal | stock_movements, stocks, audit_logs | Hujjatlar ta’siri, hisob yozuvlari | Faqat qo‘shiladi (stocks — yig‘indi) |
Buyurtma nimalardan iborat
1Raqam
BY-2026-000123 — tur, yil, ketma-ket tartib; noyob indeks bilan.2Sarlavha
3Qatorlar
order_items: mahsulot, miqdor, sotuv paytidagi narx, jami.4Holat
OrderStatus: draft → confirmed → reserved → invoiced → shipped.5Jami
total — qatorlar yig‘indisi, hujjatda saqlanadi.6Tarix
created_at, updated_at, audit jurnali.Har bir tur uchun alohida ketma-ketlik
function raqam(string $prefiks, int $yil, int $tartib): string { return sprintf('%s-%d-%06d', $prefiks, $yil, $tartib); } $oxirgi = ['BY' => 122, 'HF' => 44]; // turlar bo‘yicha hisoblagich foreach (['BY', 'BY', 'HF'] as $tur) { $oxirgi[$tur]++; echo raqam($tur, 2026, $oxirgi[$tur]), "\n"; }
BY-2026-000123 BY-2026-000124 HF-2026-000045
max(number) + qulf bilan — ikki menejer bir raqam olmasin1-bo‘lim yakuni: Ma’lumotnomalar, hujjatlar va registrlar
order_items da narx nusxa qilib saqlanadi?stocks va stock_movements qanday bog‘langan?1-topshiriq: Keyingi hujjat raqami
Hujjat raqami formati: PP-YYYY-NNNNNN (2 katta harf, yil, 6 xonali tartib), masalan BY-2026-000123. Shu turdagi oxirgi raqam (yoki null — hali hujjat yo‘q), prefiks va joriy yil berilgan. Keyingi raqamni qaytaring: yil o‘zgargan bo‘lsa tartib 000001 dan boshlanadi. Prefiks formati noto‘g‘ri, oxirgi raqam formati noto‘g‘ri yoki prefiksi boshqa bo‘lsa — InvalidArgumentException; oxirgi raqam yili joriy yildan katta yoki tartib 999999 ga yetgan bo‘lsa — DomainException.
Imzo: function keyingi_raqam(?string $oxirgi, string $prefiks, int $yil): string
Qaytaradi: Keyingi hujjat raqami satri.
keyingi_raqam('BY-2026-000123', 'BY', 2026)"BY-2026-000124"
Normalizatsiya va ustun turlari
Bitta “Excel” jadval va normal jadvallar
Noto‘g‘ri: hammasi bitta jadvalda
orders(number, mijoz_nomi, mijoz_tel, mahsulotlar, summa)mahsulotlar= “UN-001 x2, SH-002 x1” — 1NF buzilgan- Mijoz telefoni har buyurtmada takrorlanadi
- Telefon o‘zgarsa — 50 joyni yangilash kerak
To‘g‘ri: 3NF
counterparties(id, name, inn, phone)orders(id, number, counterparty_id, total)order_items(order_id, product_id, quantity, price)- Har bir fakt bitta joyda;
price— ataylab nusxa
1NF, 2NF, 3NF — buzilish va tuzatish
| Forma | Qoida | Buzilish misoli | Tuzatish |
|---|---|---|---|
| 1NF | Atomar qiymatlar, takrorlanuvchi guruh yo‘q | orders.mahsulotlar = "UN-001, SH-002" | order_items qatorlari |
| 2NF | Ustun butun kalitga bog‘liq | order_items.product_name | Nom products da |
| 3NF | Tranzitiv bog‘liqlik yo‘q | orders.counterparty_phone | Telefon counterparties da |
| Ataylab | Tarixiy fakt yoki tezlik | order_items.price, stocks | Kim yangilashi aniq yozilgan |
Baza darajasidagi himoya
CREATE TABLE order_items ( id bigserial PRIMARY KEY, order_id bigint NOT NULL REFERENCES orders (id) ON DELETE CASCADE, product_id bigint NOT NULL REFERENCES products (id), quantity integer NOT NULL CHECK (quantity > 0), price numeric(14,2) NOT NULL CHECK (price >= 0), total numeric(14,2) NOT NULL, UNIQUE (order_id, product_id) ); INSERT INTO order_items (order_id, product_id, quantity, price, total) VALUES (45, 7, 0, 15000, 0);
ERROR: new row for relation "order_items" violates check constraint "order_items_quantity_check"
Nima uchun float emas
$f = 0.0; foreach ([0.1, 0.2, 0.3] as $x) { // so‘mda, float $f += $x; } var_dump($f == 0.6); echo json_encode($f), "\n"; $t = 0; foreach ([10, 20, 30] as $x) { // tiyinda, butun son $t += $x; } var_dump($t === 60); printf("%d.%02d so‘m\n", intdiv($t, 100), $t % 100);
bool(false) 0.6000000000000001 bool(true) 0.60 so‘m
decimal ustunni satr sifatida qaytaradi — yo‘qotish yo‘q2-bo‘lim yakuni: Normalizatsiya va ustun turlari
order_items da product_name saqlash qaysi normal formani buzadi?integer emas, satr ustunida saqlanadi?orders.total ni saqlash denormalizatsiya; nima uchun u oqlanadi?2-topshiriq: Excel jadvalini normallashtirish
Eski tizimdan “tekis” qatorlar keldi: ['number' => ..., 'inn' => ..., 'mijoz' => ..., 'sku' => ..., 'miqdor' => int]. Ularni uchta jadvalga ajrating: kontragentlar (STIR bo‘yicha noyob), buyurtmalar (raqam bo‘yicha noyob) va buyurtma qatorlari. Bitta buyurtmada bir xil SKU bir necha marta kelsa — miqdorlar qo‘shiladi. Bir STIR ga turli nom yoki bitta buyurtma raqamiga turli STIR to‘g‘ri kelsa — ma’lumot ziddiyatli: DomainException.
Imzo: function normallashtir(array $qatorlar): array
Qaytaradi: ['counterparties' => [['inn', 'name'], ...], 'orders' => [['number', 'inn'], ...], 'order_items' => [['number', 'sku', 'quantity'], ...]] — kontragentlar STIR bo‘yicha, buyurtmalar raqam bo‘yicha saralangan; qatorlar birinchi uchragan tartibda. Ichki elementlar — assotsiativ massivlar shu kalitlar bilan.
normallashtir([['number' => 'BY-2026-000002', 'inn' => '301234567', 'mijoz' => 'Baraka savdo', 'sku' => 'UN-001', 'miqdor' => 5], ['number' => 'BY-2026-000001', 'inn' => '301234567', 'mijoz' => 'Baraka savdo', 'sku' => 'SH-002', 'miqdor' => 2]])
{"counterparties":[{"inn":"301234567","name":"Baraka savdo"}],"orders":[{"number":"BY-2026-000001","inn":"301234567"},{"number":"BY-2026-000002","inn":"301234567"}],"order_items":[{"number":"BY-2026-000002","sku":"UN-001","quantity":5},{"number":"BY-2026-000001","sku":"SH-002","quantity":2}]}Audit maydonlari va soft delete
Yozuvning pasporti va to‘liq tarixi
timestamps()
created_at, updated_at — Eloquent avtomatik to‘ldiradi.created_by
users.id ga tashqi kalit; creating hodisasida to‘ldiriladi.audit_logs
auditable_type, auditable_id, old_values, new_values (JSON), user_id, ip.Faqat qo‘shiladi
SoftDeletes va created_by
class Product extends Model { use HasFactory, SoftDeletes; protected static function booted(): void { static::creating(function (Product $product) { $product->created_by ??= auth()->id(); }); } } $p = Product::where('sku', 'UN-001')->first(); $p->delete(); // UPDATE ... SET deleted_at = now() Product::where('sku', 'UN-001')->first(); // null Product::withTrashed()->where('sku', 'UN-001')->first(); // topiladi Product::onlyTrashed()->count(); // 1 $p->restore(); // deleted_at = NULL
update "products" set "deleted_at" = ?, "updated_at" = ? where "id" = ? select * from "products" where "sku" = ? and "deleted_at" is null limit 1
deleted_at is null sharti qo‘shiladiSoft delete qanday filtrlaydi
$products = [ ['id' => 1, 'sku' => 'UN-001', 'deleted_at' => null], ['id' => 2, 'sku' => 'SH-002', 'deleted_at' => '2026-09-20 14:05'], ['id' => 3, 'sku' => 'YG-003', 'deleted_at' => null], ]; $tirik = fn (array $r): bool => $r['deleted_at'] === null; $ochgan = fn (array $r): bool => !$tirik($r); $sku = fn (array $r): string => implode(', ', array_column($r, 'sku')); echo 'all: ', $sku(array_filter($products, $tirik)), "\n"; echo 'with: ', $sku($products), "\n"; echo 'only: ', $sku(array_filter($products, $ochgan)), "\n";
all: UN-001, YG-003 with: UN-001, SH-002, YG-003 only: SH-002
Product::all() — faqat tirik yozuvlarProduct::withTrashed()->get() — hammasiProduct::onlyTrashed()->get() — faqat o‘chirilganlarSoft delete va UNIQUE (PostgreSQL)
-- Muammo: UN-001 o‘chirilgan, lekin qayta yaratib bo‘lmaydi INSERT INTO products (sku, name, ...) VALUES ('UN-001', ...); -- ERROR: duplicate key value violates "products_sku_unique" -- Yechim: noyoblik faqat “tirik” yozuvlar orasida DROP INDEX products_sku_unique; CREATE UNIQUE INDEX products_sku_alive_unique ON products (sku) WHERE deleted_at IS NULL;
CREATE INDEX → o‘chirilgan UN-001 qoladi, yangi UN-001 yaratiladi → ikkita tirik UN-001 baribir taqiqlangan
DB::statement('CREATE UNIQUE INDEX ...') bilanRule::unique('products')->whereNull('deleted_at')Soft delete yoki holat
✓ Soft delete — ma’lumotnomalar
products,counterparties: eski hujjatlar ularga bog‘langan- Katalog va tanlov ro‘yxatlarida ko‘rinmaydi
- Hisobotlarda
withTrashed()bilan ko‘rinadi - Xato bilan o‘chirilsa —
restore()
✗ Soft delete — hujjatlar uchun emas
- Buyurtma o‘chirilmaydi —
cancelledholatiga o‘tadi - Hisob-faktura — tuzatuvchi hujjat bilan
stock_movements,audit_logs— hech qachon o‘chirilmaydi- Qoralama (
draft) buyurtmani haqiqiy o‘chirish mumkin
3-bo‘lim yakuni: Audit maydonlari va soft delete
SoftDeletes qo‘shilgan modelda Product::find(5) o‘chirilgan yozuvni qaytaradimi?3-topshiriq: Audit uchun o‘zgarishlar farqi
Yozuvning eski va yangi atributlari berilgan. Audit jurnali uchun faqat o‘zgargan ustunlarni ajrating: new dagi har bir kalit uchun qiymat old dagidan qat’iy farq qilsa (!==), u o‘zgargan hisoblanadi; old da bo‘lmagan kalitning eski qiymati — null. $etiborsiz ro‘yxatidagi kalitlar (standart: updated_at) e’tiborga olinmaydi. old da bor, lekin new da yo‘q kalitlar ham hisobga olinmaydi.
Imzo: function audit_farq(array $old, array $new, array $etiborsiz = ['updated_at']): array
Qaytaradi: ['old_values' => [...], 'new_values' => [...]] — kalitlar new dagi tartibda.
audit_farq(['price' => '15000.00', 'name' => 'Un', 'updated_at' => '09:00'], ['price' => '16500.00', 'name' => 'Un', 'updated_at' => '10:15'])
{"old_values":{"price":"15000.00"},"new_values":{"price":"16500.00"}}Eloquent ORM
Product — fillable, casts, bog‘lanish, scope
class Product extends Model { use HasFactory, SoftDeletes; protected $fillable = ['sku', 'name', 'category_id', 'unit', 'price', 'min_stock', 'is_active']; protected function casts(): array { return ['price' => 'decimal:2', 'is_active' => 'boolean']; } public function category(): BelongsTo { return $this->belongsTo(Category::class); } public function scopeActive(Builder $query): void { $query->where('is_active', true); } }
$p->price → "15000.00" (string)
$p->is_active → true (bool)
$p->category → App\Models\Category {name: "Un mahsulotlari"}create() / fill() bilan yoziladi$casts xossasi ham ishlaydicategory_id tashqi kaliti konventsiyadanProduct::active()->get() ko‘rinishida chaqiriladiOrder — enum cast va bog‘lanishlar
class Order extends Model { protected $fillable = ['number', 'counterparty_id', 'warehouse_id', 'status', 'total', 'currency', 'created_by']; protected function casts(): array { return [ 'status' => OrderStatus::class, 'total' => 'decimal:2', ]; } public function items(): HasMany { return $this->hasMany(OrderItem::class); } }
$order->status → App\Enums\OrderStatus::Confirmed $order->status->value → "confirmed" $order->items->count() → 3
'confirmed' satri enum ga aylanadi va aksinchaorder_items.order_id bo‘yichaEager loading, filtrlar, soft delete
$orders = Order::with(['counterparty', 'items.product']) ->where('status', OrderStatus::Confirmed) ->where('created_at', '>=', now()->startOfMonth()) ->orderByDesc('id') ->get(); $soni = Product::active()->whereBelongsTo($category)->count(); $qarzdorlar = Counterparty::whereHas('orders', function ($q) { $q->where('status', OrderStatus::Invoiced); })->get();
select * from "orders" where "status" = ? and "created_at" >= ? order by "id" desc select * from "counterparties" where "id" in (3, 7, 12) select * from "order_items" where "order_id" in (41, 42, 45) select * from "products" where "id" in (...) and "deleted_at" is null
category_id = $category->id ning qisqa yozuvi4-bo‘lim yakuni: Eloquent ORM
Counterparty modeli uchun qaysi jadval nomini kutadi?$fillable va $guarded farqi nimada?Order::with('items') nima uchun kerak?Migratsiyalar
products migratsiyasi
public function up(): void { Schema::create('products', function (Blueprint $table) { $table->id(); $table->string('sku', 32)->unique(); $table->string('name'); $table->foreignId('category_id') ->constrained()->restrictOnDelete(); $table->string('unit', 8); // dona, kg, litr, quti $table->decimal('price', 14, 2); $table->unsignedInteger('min_stock')->default(0); $table->boolean('is_active')->default(true); $table->timestamps(); $table->softDeletes(); }); } // down(): Schema::dropIfExists('products');
create table "products" ("id" bigserial primary key,
"sku" varchar(32) not null, "name" varchar(255) not null,
"category_id" bigint not null, "price" decimal(14, 2) not null, ...,
"deleted_at" timestamp(0) without time zone null)
alter table "products" add constraint "products_category_id_foreign"
foreign key ("category_id") references "categories" ("id") on delete restrictcategory_id → categories.id (nom konventsiyadan)deleted_at nullable timestampstocks va stock_movements
Schema::create('stocks', function (Blueprint $table) { $table->id(); $table->foreignId('warehouse_id')->constrained(); $table->foreignId('product_id')->constrained(); $table->integer('quantity')->default(0); $table->integer('reserved')->default(0); $table->unique(['warehouse_id', 'product_id']); }); Schema::create('stock_movements', function (Blueprint $table) { $table->id(); $table->foreignId('warehouse_id')->constrained(); $table->foreignId('product_id')->constrained(); $table->string('type', 16); // in, out, reserve, release, adjust $table->integer('quantity'); $table->nullableMorphs('document'); $table->foreignId('user_id')->nullable()->constrained(); $table->timestamp('created_at')->useCurrent(); });
alter table "stocks" add constraint
"stocks_warehouse_id_product_id_unique" unique ("warehouse_id", "product_id")
create index "stock_movements_document_type_document_id_index"
on "stock_movements" ("document_type", "document_id")document_type + document_id — qaysi hujjat sababliUPDATED_AT = null)quantity >= reserved — DB::statement bilan qo‘shingMigratsiya buyruqlari
php artisan make:migration create_warehouses_table php artisan migrate php artisan migrate:status php artisan make:migration add_barcode_to_products_table php artisan migrate:rollback --step=1 # faqat lokal php artisan migrate:fresh --seed # faqat lokal!
2026_09_14_100000_create_categories_table ...... [2] Ran 2026_09_14_100100_create_products_table ........ [2] Ran 2026_09_20_090000_add_barcode_to_products_table ...... Pending
Schema::table shablonidown())Migratsiyalar bilan jamoada ishlash
Tahrirlamang
down() yozing
rollback bilan sinangTartib
Production
migrate --force; fresh taqiqlanganKatta jadval
5-bo‘lim yakuni: Migratsiyalar
foreignId('category_id')->constrained() qaysi jadvalga tashqi kalit yaratadi?migrate:rollback nimani bekor qiladi?Asosiy xulosalar
1Uch tur jadval
2Hujjat — tarix
33NF + ataylab denormalizatsiya
4To‘g‘ri turlar
5Audit va soft delete
6Eloquent va migratsiyalar
$fillable, casts(), bog‘lanishlar; sxema — versiyalangan kod, bajarilgani tahrirlanmaydi.Yakunlashdan oldin sakkizta savol
stocks alohida saqlanadi?withTrashed() nima qiladi?constrained()->restrictOnDelete() ma’nosi?3-amaliy mashg‘ulot: 5 ta PHP topshiriq va loyiha bosqichi
Model nomidan jadval nomi
Kategoriyalar daraxti yo‘llari
Ommaviy to‘ldirish ($fillable / $guarded)
Migratsiya rejasi: migrate, rollback, status
Qoldiq registrini jurnaldan tiklash
Darsni tark etishdan oldin
Javoblaringizni yozing (✎ Javob yozish) yoki qog‘ozga yozib topshiring.
sku noyobligi bilan qanday muammo chiqadi va uni qanday hal qilasiz?