\n \u0130li\u015fkisel veritabanlar\u0131, verileri d\u00fczenli ve y\u00f6netilebilir par\u00e7alar halinde depolamak i\u00e7in tablolar kullan\u0131r. Ancak, ger\u00e7ek d\u00fcnya uygulamalar\u0131nda, ihtiyac\u0131m\u0131z olan bilgiler genellikle birden fazla tabloya da\u011f\u0131lm\u0131\u015f durumdad\u0131r. \u0130\u015fte tam bu noktada SQL JOIN’lar devreye girer. SQL JOIN’lar, farkl\u0131 tablolardaki ilgili verileri tek bir sonu\u00e7 k\u00fcmesinde birle\u015ftirmemizi sa\u011flayan g\u00fc\u00e7l\u00fc ara\u00e7lard\u0131r. Bu makalede, SQL JOIN’lar\u0131n ne oldu\u011funu, neden bu kadar \u00f6nemli olduklar\u0131n\u0131, farkl\u0131 JOIN t\u00fcrlerini ve her birinin nas\u0131l kullan\u0131ld\u0131\u011f\u0131n\u0131 detayl\u0131 kod \u00f6rnekleriyle ele alaca\u011f\u0131z. Veritaban\u0131 y\u00f6netiminde etkin bir \u015fekilde veri \u00e7ekmek ve analiz etmek i\u00e7in JOIN’lar\u0131 anlamak, her SQL kullan\u0131c\u0131s\u0131 i\u00e7in vazge\u00e7ilmez bir beceridir.\n<\/p>\n
\n Modern uygulamalar\u0131n \u00e7o\u011fu, verilerini d\u00fczenli ve mant\u0131ksal bir yap\u0131da tutmak i\u00e7in ili\u015fkisel veritaban\u0131 y\u00f6netim sistemlerini (RDBMS) kullan\u0131r. Bu sistemlerde veriler, belirli ili\u015fkilerle birbirine ba\u011fl\u0131 olan ayr\u0131 tablolarda saklan\u0131r. \u00d6rne\u011fin, bir e-ticaret uygulamas\u0131nda m\u00fc\u015fteri bilgileri bir tabloda, sipari\u015f bilgileri ba\u015fka bir tabloda ve \u00fcr\u00fcn bilgileri bamba\u015fka bir tabloda yer alabilir. Ancak, “Hangi m\u00fc\u015fteri hangi \u00fcr\u00fcnleri sipari\u015f etti?” gibi sorular\u0131 yan\u0131tlamak i\u00e7in bu farkl\u0131 tablolardaki verileri bir araya getirmemiz gerekir. SQL JOIN’lar, bu ihtiyac\u0131 kar\u015f\u0131lamak i\u00e7in tasarlanm\u0131\u015ft\u0131r.\n<\/p>\n
\n \u0130li\u015fkisel veritabanlar\u0131, veri tekrar\u0131n\u0131 (redundancy) azaltmak, veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc sa\u011flamak ve y\u00f6netimi kolayla\u015ft\u0131rmak amac\u0131yla normalizasyon prensiplerine g\u00f6re tasarlan\u0131r. Bu, ayn\u0131 t\u00fcrden bilgilerin tek bir yerde tutulmas\u0131 ve di\u011fer tablolardan bu bilgilere anahtarlar (primary\/foreign keys) arac\u0131l\u0131\u011f\u0131yla referans verilmesi anlam\u0131na gelir. Bu yap\u0131, verimli depolama ve tutarl\u0131l\u0131k sa\u011flarken, farkl\u0131 tablolardaki verileri birle\u015ftirmek i\u00e7in \u00f6zel komutlara ihtiya\u00e7 duyar. JOIN’lar, bu anahtar ili\u015fkilerini kullanarak tablolardaki sat\u0131rlar\u0131 mant\u0131ksal olarak birle\u015ftirir.\n<\/p>\n
\n SQL, farkl\u0131 veri birle\u015ftirme senaryolar\u0131na uygun \u00e7e\u015fitli JOIN t\u00fcrleri sunar. Her bir JOIN t\u00fcr\u00fc, birle\u015ftirme ko\u015fulunu kar\u015f\u0131layan sat\u0131rlar\u0131n yan\u0131 s\u0131ra, bir ko\u015fulu kar\u015f\u0131lamayan sat\u0131rlar\u0131n da sonu\u00e7 k\u00fcmesinde nas\u0131l yer alaca\u011f\u0131n\u0131 belirler. Ba\u015fl\u0131ca JOIN t\u00fcrleri \u015funlard\u0131r:\n<\/p>\n
INNER JOIN<\/code>: Her iki tabloda da e\u015fle\u015fen kay\u0131tlara sahip sat\u0131rlar\u0131 d\u00f6nd\u00fcr\u00fcr.<\/li>\nLEFT JOIN<\/code> (veya LEFT OUTER JOIN<\/code>): Sol tablodaki t\u00fcm kay\u0131tlar\u0131 ve sa\u011f tabloda e\u015fle\u015fen kay\u0131tlar\u0131 d\u00f6nd\u00fcr\u00fcr. E\u015fle\u015fme yoksa, sa\u011f tablodan NULL de\u011ferler gelir.<\/li>\nRIGHT JOIN<\/code> (veya RIGHT OUTER JOIN<\/code>): Sa\u011f tablodaki t\u00fcm kay\u0131tlar\u0131 ve sol tabloda e\u015fle\u015fen kay\u0131tlar\u0131 d\u00f6nd\u00fcr\u00fcr. E\u015fle\u015fme yoksa, sol tablodan NULL de\u011ferler gelir.<\/li>\nFULL OUTER JOIN<\/code>: Her iki tablodaki t\u00fcm kay\u0131tlar\u0131 d\u00f6nd\u00fcr\u00fcr. E\u015fle\u015fme yoksa, di\u011fer tablodan NULL de\u011ferler gelir.<\/li>\nCROSS JOIN<\/code>: \u0130ki tablonun Kartezyen \u00e7arp\u0131m\u0131n\u0131 d\u00f6nd\u00fcr\u00fcr; yani ilk tablonun her sat\u0131r\u0131n\u0131 ikinci tablonun her sat\u0131r\u0131yla birle\u015ftirir.<\/li>\nSELF JOIN<\/code>: Bir tablonun kendisiyle birle\u015ftirilmesidir.<\/li>\n<\/ul>\nTemel JOIN S\u00f6zdizimi<\/h4>\n
\n SQL JOIN’lar\u0131n genel s\u00f6zdizimi olduk\u00e7a basittir. Genellikle SELECT<\/code> ifadesiyle birlikte kullan\u0131l\u0131r ve FROM<\/code> ile JOIN<\/code> anahtar kelimeleriyle tablolara ve birle\u015ftirme ko\u015fullar\u0131na i\u015faret eder:\n<\/p>\n\nSELECT kolon1, kolon2, ...\nFROM tablo1\nJOIN_T\u00dcR\u00dc tablo2 ON tablo1.ortak_kolon = tablo2.ortak_kolon;\n<\/pre>\n<\/code><\/p>\n
\n Burada JOIN_T\u00dcR\u00dc<\/code> yerine yukar\u0131da bahsedilen INNER<\/code>, LEFT<\/code>, RIGHT<\/code>, FULL OUTER<\/code> veya CROSS<\/code> gibi anahtar kelimeler gelir. ON<\/code> ifadesi ise birle\u015ftirme ko\u015fulunu belirtir.\n<\/p>\nINNER JOIN: Ortak Verileri Ke\u015ffetmek<\/h3>\n
\n INNER JOIN<\/code>, SQL JOIN t\u00fcrleri aras\u0131nda en s\u0131k kullan\u0131lan\u0131d\u0131r ve varsay\u0131lan JOIN t\u00fcr\u00fcd\u00fcr. \u0130ki veya daha fazla tabloyu, belirtilen bir ko\u015fula g\u00f6re birle\u015ftirir ve yaln\u0131zca her iki tabloda da e\u015fle\u015fen kay\u0131tlara sahip sat\u0131rlar\u0131 sonu\u00e7 k\u00fcmesine dahil eder. E\u011fer bir tabloda e\u015fle\u015fen bir kay\u0131t yoksa, o kay\u0131t sonu\u00e7 k\u00fcmesinde yer almaz.\n<\/p>\n\u00c7al\u0131\u015fma Mant\u0131\u011f\u0131 ve Kullan\u0131m Alanlar\u0131<\/h4>\n
\n INNER JOIN<\/code>, k\u00fcmeler teorisindeki kesi\u015fim (intersection) i\u015flemine benzer. Yaln\u0131zca her iki k\u00fcmede de (yani her iki tabloda da) ortak olan elemanlar\u0131 (yani sat\u0131rlar\u0131) getirir. Bu, genellikle bir anahtar (foreign key) arac\u0131l\u0131\u011f\u0131yla birbirine ba\u011fl\u0131 olan tablolardan kesin e\u015fle\u015fmelerin gerekti\u011fi durumlarda idealdir. \u00d6rne\u011fin, sadece sipari\u015f vermi\u015f m\u00fc\u015fterilerin listesini g\u00f6rmek istedi\u011fimizde INNER JOIN<\/code> kullan\u0131r\u0131z.\n<\/p>\n\n Kullan\u0131m Alanlar\u0131:<\/strong>\n<\/p>\n\n- Sipari\u015f veren m\u00fc\u015fterileri listelemek.<\/li>\n
- Belirli bir \u00fcr\u00fcn kategorisindeki \u00fcr\u00fcnlerin tedarik\u00e7ilerini bulmak.<\/li>\n
- \u00c7al\u0131\u015fanlar\u0131n departman bilgileriyle birlikte listelemek.<\/li>\n<\/ul>\n
Kod \u00d6rne\u011fi<\/h4>\n
\n A\u015fa\u011f\u0131daki \u00f6rnekte, Musteriler<\/code> ve Siparisler<\/code> tablolar\u0131n\u0131 MusteriID<\/code> kolonunu kullanarak birle\u015ftiriyoruz.\n<\/p>\n\n-- Varsay\u0131lan INNER JOIN kullan\u0131m\u0131\nSELECT\n M.Ad,\n M.Soyad,\n S.SiparisID,\n S.SiparisTarihi,\n S.ToplamTutar\nFROM\n Musteriler M\nINNER JOIN\n Siparisler S ON M.MusteriID = S.MusteriID;\n<\/pre>\n<\/code><\/p>\n
\n Bu sorgu, hem Musteriler<\/code> tablosunda bulunan hem de Siparisler<\/code> tablosunda ilgili bir sipari\u015fi olan m\u00fc\u015fterilerin ad\u0131n\u0131, soyad\u0131n\u0131 ve sipari\u015f bilgilerini getirecektir. Sipari\u015fi olmayan m\u00fc\u015fteriler veya m\u00fc\u015fterisi olmayan sipari\u015fler (veri tutars\u0131zl\u0131\u011f\u0131 durumunda) sonu\u00e7 k\u00fcmesinde yer almayacakt\u0131r.\n<\/p>\nLEFT JOIN ve RIGHT JOIN: Veri Kapsam\u0131n\u0131 Geni\u015fletmek<\/h3>\n
\n INNER JOIN<\/code> sadece e\u015fle\u015fen kay\u0131tlar\u0131 getirirken, LEFT JOIN<\/code> ve RIGHT JOIN<\/code> (genellikle OUTER JOIN<\/code> olarak da adland\u0131r\u0131l\u0131rlar) e\u015fle\u015fmeyen kay\u0131tlar\u0131 da belirli bir y\u00f6nden dahil etme esnekli\u011fi sunar. Bu, belirli bir tablonun t\u00fcm kay\u0131tlar\u0131n\u0131 g\u00f6rmek istedi\u011fimizde ve di\u011fer tablodan gelen verilerin mevcut olup olmad\u0131\u011f\u0131na bakmaks\u0131z\u0131n bu kay\u0131tlar\u0131 listelemek istedi\u011fimizde \u00e7ok kullan\u0131\u015fl\u0131d\u0131r.\n<\/p>\nLEFT JOIN: Sol Tablonun T\u00fcm Kay\u0131tlar\u0131<\/h4>\n
\n LEFT JOIN<\/code> (veya LEFT OUTER JOIN<\/code>), sol tablodaki t\u00fcm kay\u0131tlar\u0131 sonu\u00e7 k\u00fcmesine dahil eder. Sa\u011f tablodan ise yaln\u0131zca birle\u015ftirme ko\u015fulunu kar\u015f\u0131layan e\u015fle\u015fen kay\u0131tlar\u0131 getirir. E\u011fer sol tablodaki bir kay\u0131t i\u00e7in sa\u011f tabloda e\u015fle\u015fen bir kay\u0131t bulunamazsa, sa\u011f tablonun kolonlar\u0131 i\u00e7in sonu\u00e7 k\u00fcmesinde NULL<\/code> de\u011ferler g\u00f6sterilir.\n<\/p>\n\n Kullan\u0131m Alanlar\u0131:<\/strong>\n<\/p>\n\n- T\u00fcm m\u00fc\u015fterileri ve varsa sipari\u015flerini listelemek (sipari\u015f vermemi\u015f m\u00fc\u015fteriler de dahil).<\/li>\n
- T\u00fcm \u00fcr\u00fcnleri ve varsa ilgili yorumlar\u0131n\u0131 g\u00f6stermek.<\/li>\n
- Bir departmandaki t\u00fcm \u00e7al\u0131\u015fanlar\u0131 listelemek, hen\u00fcz bir projeye atanmam\u0131\u015f olsalar bile.<\/li>\n<\/ul>\n
RIGHT JOIN: Sa\u011f Tablonun T\u00fcm Kay\u0131tlar\u0131<\/h4>\n
\n RIGHT JOIN<\/code> (veya RIGHT OUTER JOIN<\/code>), LEFT JOIN<\/code>'in tam tersidir. Sa\u011f tablodaki t\u00fcm kay\u0131tlar\u0131 sonu\u00e7 k\u00fcmesine dahil ederken, sol tablodan yaln\u0131zca e\u015fle\u015fen kay\u0131tlar\u0131 getirir. Sa\u011f tablodaki bir kay\u0131t i\u00e7in sol tabloda e\u015fle\u015fme bulunamazsa, sol tablonun kolonlar\u0131 i\u00e7in NULL<\/code> de\u011ferler g\u00f6sterilir. RIGHT JOIN<\/code> genellikle LEFT JOIN<\/code> ile ayn\u0131 sonu\u00e7lar\u0131 verecek \u015fekilde yeniden yaz\u0131labilir; sadece tablo s\u0131ralamas\u0131 de\u011fi\u015fir.\n<\/p>\n\n Kullan\u0131m Alanlar\u0131:<\/strong>\n<\/p>\n\n- T\u00fcm sipari\u015fleri ve varsa ilgili m\u00fc\u015fteri bilgilerini listelemek (m\u00fc\u015fterisi silinmi\u015f sipari\u015fler de dahil, e\u011fer referans anahtar k\u0131s\u0131tlamalar\u0131 buna izin veriyorsa).<\/li>\n
- T\u00fcm kategorileri ve varsa ilgili \u00fcr\u00fcnleri listelemek.<\/li>\n<\/ul>\n
Kar\u015f\u0131la\u015ft\u0131rmal\u0131 \u00d6rnekler<\/h4>\n
\n Yine Musteriler<\/code> ve Siparisler<\/code> tablolar\u0131n\u0131 kullanarak \u00f6rnekler verelim:\n<\/p>\n\n-- LEFT JOIN \u00d6rne\u011fi: T\u00fcm m\u00fc\u015fterileri ve varsa sipari\u015flerini getir\nSELECT\n M.Ad,\n M.Soyad,\n S.SiparisID,\n S.SiparisTarihi,\n S.ToplamTutar\nFROM\n Musteriler M\nLEFT JOIN\n Siparisler S ON M.MusteriID = S.MusteriID;\n\n-- RIGHT JOIN \u00d6rne\u011fi: T\u00fcm sipari\u015fleri ve varsa m\u00fc\u015fteri bilgilerini getir\nSELECT\n M.Ad,\n M.Soyad,\n S.SiparisID,\n S.SiparisTarihi,\n S.ToplamTutar\nFROM\n Musteriler M\nRIGHT JOIN\n Siparisler S ON M.MusteriID = S.MusteriID;\n<\/pre>\n<\/code><\/p>\n
\n \u0130lk sorgu (LEFT JOIN<\/code>), sipari\u015f vermemi\u015f m\u00fc\u015fterileri de listeler ve bu m\u00fc\u015fteriler i\u00e7in SiparisID<\/code>, SiparisTarihi<\/code> ve ToplamTutar<\/code> kolonlar\u0131 NULL<\/code> olacakt\u0131r. \u0130kinci sorgu (RIGHT JOIN<\/code>), e\u011fer bir sipari\u015fin ili\u015fkili oldu\u011fu m\u00fc\u015fteri Musteriler<\/code> tablosundan silinmi\u015fse (veya hi\u00e7 eklenmemi\u015fse), bu sipari\u015fleri de listeler ve ilgili m\u00fc\u015fteri kolonlar\u0131 NULL<\/code> olacakt\u0131r.\n<\/p>\nFULL OUTER JOIN: T\u00fcm Verilerin Birle\u015fimi<\/h3>\n
\n FULL OUTER JOIN<\/code>, LEFT JOIN<\/code> ve RIGHT JOIN<\/code>'in birle\u015fimi gibidir. Her iki tablodaki t\u00fcm kay\u0131tlar\u0131 sonu\u00e7 k\u00fcmesine dahil eder. E\u011fer bir tabloda e\u015fle\u015fen bir kay\u0131t yoksa, di\u011fer tablonun kolonlar\u0131 i\u00e7in NULL<\/code> de\u011ferler g\u00f6sterilir. Bu, iki k\u00fcmenin birle\u015fimine (union) benzer bir sonu\u00e7 \u00fcretir.\n<\/p>\nKapsaml\u0131 Birle\u015ftirme Mant\u0131\u011f\u0131<\/h4>\n
\n FULL OUTER JOIN<\/code>, birle\u015ftirme ko\u015fulunu kar\u015f\u0131layan t\u00fcm sat\u0131rlar\u0131 getirir. Ayr\u0131ca, sol tabloda olup sa\u011f tabloda e\u015fle\u015fmesi olmayan t\u00fcm sat\u0131rlar\u0131 (sa\u011f taraftan NULL de\u011ferlerle) ve sa\u011f tabloda olup sol tabloda e\u015fle\u015fmesi olmayan t\u00fcm sat\u0131rlar\u0131 (sol taraftan NULL de\u011ferlerle) getirir. Bu, her iki tablodaki t\u00fcm veriyi tek bir g\u00f6r\u00fcn\u00fcmde birle\u015ftirmek istedi\u011fimizde kullan\u0131\u015fl\u0131d\u0131r.\n<\/p>\nKullan\u0131m Senaryolar\u0131 ve Dikkat Edilmesi Gerekenler<\/h4>\n
\n Kullan\u0131m Alanlar\u0131:<\/strong>\n<\/p>\n\n- \u0130ki farkl\u0131 listenin (\u00f6rne\u011fin, potansiyel m\u00fc\u015fteriler ve mevcut m\u00fc\u015fteriler) t\u00fcm \u00fcyelerini ve varsa ortak \u00f6zelliklerini g\u00f6rmek.<\/li>\n
- \u0130ki farkl\u0131 sistemden gelen veri k\u00fcmelerini kar\u015f\u0131la\u015ft\u0131rmak ve eksiklikleri tespit etmek.<\/li>\n
- Birle\u015ftirme ko\u015fulu \u00fczerinde tam bir resim elde etmek istedi\u011fimizde.<\/li>\n<\/ul>\n
\n Dikkat Edilmesi Gerekenler:<\/strong>\n<\/p>\n\nFULL OUTER JOIN<\/code>, b\u00fcy\u00fck veri k\u00fcmelerinde performans sorunlar\u0131na yol a\u00e7abilir \u00e7\u00fcnk\u00fc \u00e7ok say\u0131da sat\u0131r d\u00f6nd\u00fcrebilir.<\/li>\n- Sonu\u00e7 k\u00fcmesinde \u00e7ok fazla
NULL<\/code> de\u011fer i\u00e7erebilir, bu da verilerin yorumlanmas\u0131n\u0131 zorla\u015ft\u0131rabilir.<\/li>\n- T\u00fcm veritaban\u0131 sistemleri
FULL OUTER JOIN<\/code>'u do\u011frudan desteklemeyebilir (\u00f6rne\u011fin, MySQL do\u011frudan desteklemez, ancak UNION<\/code> ile sim\u00fcle edilebilir).<\/li>\n<\/ul>\nKod \u00d6rne\u011fi<\/h4>\n
\n Musteriler<\/code> ve Siparisler<\/code> tablolar\u0131 i\u00e7in FULL OUTER JOIN<\/code> \u00f6rne\u011fi:\n<\/p>\n\n-- FULL OUTER JOIN \u00d6rne\u011fi\nSELECT\n M.Ad,\n M.Soyad,\n S.SiparisID,\n S.SiparisTarihi,\n S.ToplamTutar\nFROM\n Musteriler M\nFULL OUTER JOIN\n Siparisler S ON M.MusteriID = S.MusteriID;\n<\/pre>\n<\/code><\/p>\n
\n Bu sorgu, t\u00fcm m\u00fc\u015fterileri (sipari\u015fleri olsa da olmasa da) ve t\u00fcm sipari\u015fleri (m\u00fc\u015fterileri olsa da olmasa da) listeler. E\u011fer bir m\u00fc\u015fteri sipari\u015f vermemi\u015fse, sipari\u015f kolonlar\u0131 NULL<\/code> olur. E\u011fer bir sipari\u015fin m\u00fc\u015fterisi yoksa, m\u00fc\u015fteri kolonlar\u0131 NULL<\/code> olur.\n<\/p>\nCROSS JOIN ve SELF JOIN: \u00d6zel Birle\u015ftirme Teknikleri<\/h3>\n
\n SQL JOIN'lar sadece anahtar ili\u015fkilerine dayal\u0131 birle\u015ftirmelerle s\u0131n\u0131rl\u0131 de\u011fildir. Baz\u0131 \u00f6zel senaryolar i\u00e7in CROSS JOIN<\/code> ve SELF JOIN<\/code> gibi daha ni\u015f birle\u015ftirme teknikleri mevcuttur. Bu teknikler, belirli problem t\u00fcrlerini \u00e7\u00f6zmek i\u00e7in benzersiz yakla\u015f\u0131mlar sunar.\n<\/p>\nCROSS JOIN: Kartesyen \u00c7arp\u0131m<\/h4>\n
\n CROSS JOIN<\/code>, iki tablonun Kartezyen \u00e7arp\u0131m\u0131n\u0131 \u00fcretir. Bu, ilk tablodaki her sat\u0131r\u0131n, ikinci tablodaki her sat\u0131rla birle\u015ftirilmesi anlam\u0131na gelir. Sonu\u00e7 k\u00fcmesindeki sat\u0131r say\u0131s\u0131, ilk tablonun sat\u0131r say\u0131s\u0131 ile ikinci tablonun sat\u0131r say\u0131s\u0131n\u0131n \u00e7arp\u0131m\u0131na e\u015fittir. CROSS JOIN<\/code> genellikle bir ON<\/code> ko\u015fulu gerektirmez.\n<\/p>\n\n Kullan\u0131m Alanlar\u0131:<\/strong>\n<\/p>\n\n- T\u00fcm olas\u0131 kombinasyonlar\u0131 olu\u015fturmak (\u00f6rne\u011fin, t\u00fcm \u00fcr\u00fcnler ve t\u00fcm renkler i\u00e7in stok kombinasyonlar\u0131).<\/li>\n
- Test verisi olu\u015fturmak.<\/li>\n
- Belirli bir senaryoda t\u00fcm olas\u0131 e\u015fle\u015fmeleri g\u00f6rmek.<\/li>\n<\/ul>\n
\n-- CROSS JOIN \u00d6rne\u011fi\nSELECT\n M.Ad,\n P.UrunAdi\nFROM\n Musteriler M\nCROSS JOIN\n Urunler P; -- Urunler tablosu oldu\u011funu varsayal\u0131m\n<\/pre>\n<\/code><\/p>\n
\n Bu sorgu, her bir m\u00fc\u015fteriyi her bir \u00fcr\u00fcnle e\u015fle\u015ftirerek, her m\u00fc\u015fterinin her \u00fcr\u00fcn\u00fc sat\u0131n alma potansiyelini g\u00f6steren bir liste olu\u015fturur. Genellikle \u00e7ok b\u00fcy\u00fck sonu\u00e7 k\u00fcmeleri \u00fcretebilece\u011fi i\u00e7in dikkatli kullan\u0131lmal\u0131d\u0131r.\n<\/p>\n
SELF JOIN: Tablonun Kendisiyle Birle\u015ftirilmesi<\/h4>\n
\n SELF JOIN<\/code>, bir tablonun kendisiyle birle\u015ftirilmesidir. Bu, ayn\u0131 tablodaki sat\u0131rlar\u0131 belirli bir ko\u015fula g\u00f6re kar\u015f\u0131la\u015ft\u0131rmak veya ili\u015fkilendirmek istedi\u011fimizde kullan\u0131l\u0131r. SELF JOIN<\/code> yaparken, tablonun iki farkl\u0131 kopyas\u0131na farkl\u0131 takma adlar (alias) vermek zorunludur, b\u00f6ylece hangi kolonun hangi kopyadan geldi\u011fi net olur.\n<\/p>\n\n Kullan\u0131m Alanlar\u0131:<\/strong>\n<\/p>\n\n- Bir \u00e7al\u0131\u015fan\u0131n y\u00f6neticisini bulmak (y\u00f6netici de ayn\u0131 tabloda bir \u00e7al\u0131\u015fand\u0131r).<\/li>\n
- Ayn\u0131 \u015fehirde ya\u015fayan m\u00fc\u015fterileri bulmak.<\/li>\n
- Bir \u00fcr\u00fcn\u00fcn benzer \u00fcr\u00fcnlerini listelemek.<\/li>\n<\/ul>\n
\n-- SELF JOIN \u00d6rne\u011fi: Ayn\u0131 \u015fehirde ya\u015fayan m\u00fc\u015fterileri bulma\nSELECT\n M1.Ad AS Musteri1_Ad,\n M1.Soyad AS Musteri1_Soyad,\n M2.Ad AS Musteri2_Ad,\n M2.Soyad AS Musteri2_Soyad,\n M1.Sehir\nFROM\n Musteriler M1\nINNER JOIN\n Musteriler M2 ON M1.Sehir = M2.Sehir\n AND M1.MusteriID <> M2.MusteriID;\n<\/pre>\n<\/code><\/p>\n
\n Bu sorgu, ayn\u0131 \u015fehirde ya\u015fayan farkl\u0131 m\u00fc\u015fterileri listeler. M1.MusteriID <> M2.MusteriID<\/code> ko\u015fulu, bir m\u00fc\u015fterinin kendisiyle e\u015fle\u015fmesini engeller.\n<\/p>\nJOIN Optimizasyonu ve En \u0130yi Uygulamalar<\/h3>\n
\n SQL JOIN'lar veritaban\u0131 sorgular\u0131n\u0131n temelini olu\u015ftursa da, yanl\u0131\u015f kullan\u0131ld\u0131\u011f\u0131nda veya optimize edilmedi\u011finde ciddi performans sorunlar\u0131na yol a\u00e7abilir. B\u00fcy\u00fck veri k\u00fcmeleriyle \u00e7al\u0131\u015f\u0131rken, JOIN'lar\u0131n etkinli\u011fini art\u0131rmak i\u00e7in baz\u0131 en iyi uygulamalar\u0131 takip etmek hayati \u00f6nem ta\u015f\u0131r.\n<\/p>\n
\u0130ndekslerin \u00d6nemi<\/h4>\n
\n JOIN operasyonlar\u0131n\u0131n performans\u0131n\u0131 do\u011frudan etkileyen en kritik fakt\u00f6rlerden biri indekslerdir. Birle\u015ftirme ko\u015fulunda kullan\u0131lan kolonlar (genellikle foreign key kolonlar\u0131), indekslenmi\u015f oldu\u011funda veritaban\u0131 sistemi e\u015fle\u015fen sat\u0131rlar\u0131 \u00e7ok daha h\u0131zl\u0131 bulabilir.\n<\/p>\n
\n- Foreign Key Kolonlar\u0131n\u0131 \u0130ndeksleyin:<\/strong> Bir\u00e7ok veritaban\u0131 sistemi, foreign key tan\u0131mland\u0131\u011f\u0131nda otomatik olarak indeks olu\u015fturmaz. Bu kolonlar\u0131 manuel olarak indekslemek, JOIN performans\u0131n\u0131 \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131r\u0131r.<\/li>\n
- Primary Key Kolonlar\u0131:<\/strong> Primary key kolonlar\u0131 genellikle otomatik olarak indekslenir ve JOIN'larda birincil anahtar olarak kullan\u0131ld\u0131\u011f\u0131nda zaten h\u0131zl\u0131d\u0131r.<\/li>\n
- WHERE ve ORDER BY Ko\u015fullar\u0131:<\/strong> JOIN'lardan sonra gelen
WHERE<\/code> ve ORDER BY<\/code> ko\u015fullar\u0131nda kullan\u0131lan kolonlar\u0131 da indekslemek, sorgunun genel performans\u0131n\u0131 iyile\u015ftirir.<\/li>\n<\/ul>\nPerformans \u0130pu\u00e7lar\u0131<\/h4>\n\n- Gereksiz JOIN'lardan Ka\u00e7\u0131n\u0131n:<\/strong> Yaln\u0131zca ger\u00e7ekten ihtiyac\u0131n\u0131z olan tablolar\u0131 JOIN edin. Her eklenen JOIN, sorgunun karma\u015f\u0131kl\u0131\u011f\u0131n\u0131 ve dolay\u0131s\u0131yla \u00e7al\u0131\u015fma s\u00fcresini art\u0131r\u0131r.<\/li>\n
- Do\u011fru JOIN T\u00fcr\u00fcn\u00fc Se\u00e7in:<\/strong> \u0130htiyac\u0131n\u0131za en uygun JOIN t\u00fcr\u00fcn\u00fc kullan\u0131n. \u00d6rne\u011fin, sadece e\u015fle\u015fen kay\u0131tlar gerekiyorsa
INNER JOIN<\/code> kullanmak, OUTER JOIN<\/code>'a g\u00f6re daha verimli olabilir.<\/li>\n- JOIN Ko\u015fullar\u0131n\u0131 Basit Tutun:<\/strong>
ON<\/code> ifadesindeki ko\u015fullar m\u00fcmk\u00fcn oldu\u011funca basit ve indekslenebilir olmal\u0131d\u0131r. Fonksiyonlar veya karma\u015f\u0131k hesaplamalar i\u00e7eren ko\u015fullardan ka\u00e7\u0131n\u0131n.<\/li>\n- K\u00fc\u00e7\u00fck Tablolarla Ba\u015flay\u0131n:<\/strong> Sorgu planlay\u0131c\u0131n\u0131n i\u015fini kolayla\u015ft\u0131rmak i\u00e7in, genellikle daha az sat\u0131ra sahip olan tabloyu
FROM<\/code> ifadesinde ilk olarak belirtmek ve di\u011fer tablolar\u0131 ona JOIN etmek iyi bir strateji olabilir.<\/li>\n- Kolon Se\u00e7imini Optimize Edin:<\/strong>
SELECT *<\/code> yerine, sadece ger\u00e7ekten ihtiyac\u0131n\u0131z olan kolonlar\u0131 se\u00e7in. Bu, a\u011f trafi\u011fini azalt\u0131r ve sorgu i\u015fleme s\u00fcresini k\u0131salt\u0131r.<\/li>\n- Subquery'ler ve CTE'ler (Ortak Tablo \u0130fadeleri):<\/strong> Karma\u015f\u0131k sorgular\u0131 daha k\u00fc\u00e7\u00fck, y\u00f6netilebilir par\u00e7alara b\u00f6lmek i\u00e7in subquery'ler veya CTE'ler kullanmak, hem okunabilirli\u011fi art\u0131r\u0131r hem de bazen performans\u0131 iyile\u015ftirebilir.<\/li>\n<\/ul>\n
\u00c7oklu Tablo Birle\u015ftirmeleri<\/h4>\n
\n Ger\u00e7ek d\u00fcnya senaryolar\u0131nda, genellikle ikiden fazla tabloyu birle\u015ftirmeniz gerekir. SQL, birden fazla JOIN<\/code> ifadesini art arda kullanarak bu t\u00fcr karma\u015f\u0131k birle\u015ftirmelere olanak tan\u0131r.\n<\/p>\n\nSELECT\n M.Ad,\n S.SiparisID,\n U.UrunAdi,\n SD.Miktar\nFROM\n Musteriler M\nINNER JOIN\n Siparisler S ON M.MusteriID = S.MusteriID\nINNER JOIN\n SiparisDetay SD ON S.SiparisID = SD.SiparisID\nINNER JOIN\n Urunler U ON SD.UrunID = U.UrunID;\n<\/pre>\n<\/code><\/p>\n
\n Bu \u00f6rnek, bir m\u00fc\u015fterinin sipari\u015f etti\u011fi \u00fcr\u00fcnlerin detaylar\u0131n\u0131 getirmek i\u00e7in d\u00f6rt farkl\u0131 tabloyu birle\u015ftirir. Her bir JOIN<\/code>, bir \u00f6nceki birle\u015ftirilmi\u015f sonu\u00e7 k\u00fcmesine uygulan\u0131r. Performans ipu\u00e7lar\u0131, \u00e7oklu JOIN'larda daha da kritik hale gelir.\n<\/p>\nSonu\u00e7<\/h2>\n
\n SQL JOIN'lar, ili\u015fkisel veritabanlar\u0131n\u0131n kalbinde yer alan, farkl\u0131 tablolardaki verileri anlaml\u0131 bir \u015fekilde birle\u015ftirmemizi sa\u011flayan temel ve g\u00fc\u00e7l\u00fc ara\u00e7lard\u0131r. Bu makalede ele ald\u0131\u011f\u0131m\u0131z INNER JOIN<\/code>, LEFT JOIN<\/code>, RIGHT JOIN<\/code>, FULL OUTER JOIN<\/code>, CROSS JOIN<\/code> ve SELF JOIN<\/code> t\u00fcrlerinin her biri, belirli veri birle\u015ftirme senaryolar\u0131na y\u00f6nelik \u00e7\u00f6z\u00fcmler sunar. Do\u011fru JOIN t\u00fcr\u00fcn\u00fc se\u00e7mek, birle\u015ftirme ko\u015fullar\u0131n\u0131 optimize etmek ve indekslerden etkin bir \u015fekilde yararlanmak, sorgular\u0131n\u0131z\u0131n performans\u0131n\u0131 ve verimlili\u011fini do\u011frudan etkileyecektir. Veritaban\u0131 y\u00f6netiminde ustala\u015fmak ve karma\u015f\u0131k veri sorular\u0131n\u0131 yan\u0131tlamak i\u00e7in JOIN'lar\u0131 derinlemesine anlamak ve do\u011fru kullanmak vazge\u00e7ilmez bir beceridir.\n<\/p>\nSSS (S\u0131k Sorulan Sorular)<\/h2>\nINNER JOIN ile LEFT JOIN aras\u0131ndaki temel fark nedir?<\/h3>\n
\n INNER JOIN<\/code>, yaln\u0131zca her iki tabloda da e\u015fle\u015fen kay\u0131tlara sahip sat\u0131rlar\u0131 d\u00f6nd\u00fcr\u00fcr. E\u011fer bir tabloda e\u015fle\u015fen bir kay\u0131t yoksa, o sat\u0131r sonu\u00e7 k\u00fcmesinde yer almaz. LEFT JOIN<\/code> ise sol tablodaki t\u00fcm kay\u0131tlar\u0131 d\u00f6nd\u00fcr\u00fcr ve sa\u011f tablodan yaln\u0131zca e\u015fle\u015fenleri getirir. Sol tablodaki bir kay\u0131t i\u00e7in sa\u011f tabloda e\u015fle\u015fme yoksa, sa\u011f tablonun kolonlar\u0131 i\u00e7in NULL<\/code> de\u011ferler g\u00f6sterilir.\n<\/p>\nFULL OUTER JOIN'\u0131 ne zaman kullanmal\u0131y\u0131m?<\/h3>\n
\n FULL OUTER JOIN<\/code>'\u0131, her iki tablodaki t\u00fcm kay\u0131tlar\u0131 g\u00f6rmek istedi\u011finizde, e\u015fle\u015fme olup olmad\u0131\u011f\u0131na bak\u0131lmaks\u0131z\u0131n kullanmal\u0131s\u0131n\u0131z. Bu, iki veri k\u00fcmesini kar\u015f\u0131la\u015ft\u0131rmak, eksik verileri tespit etmek veya her iki tablonun birle\u015fimini tek bir g\u00f6r\u00fcn\u00fcmde sunmak istedi\u011finizde idealdir. Ancak, b\u00fcy\u00fck veri k\u00fcmelerinde performans ve NULL de\u011ferlerin yorumlanmas\u0131 a\u00e7\u0131s\u0131ndan dikkatli olunmal\u0131d\u0131r.\n<\/p>\nBirden fazla tabloyu birle\u015ftirebilir miyim?<\/h3>\n
\n Evet, SQL'de birden fazla JOIN<\/code> ifadesini art arda kullanarak ikiden fazla tabloyu birle\u015ftirebilirsiniz. Her bir JOIN<\/code>, bir \u00f6nceki birle\u015ftirilmi\u015f sonucun \u00fczerine uygulan\u0131r. Bu, karma\u015f\u0131k veri modellerinden bilgi \u00e7ekmek i\u00e7in yayg\u0131n bir y\u00f6ntemdir.\n<\/p>\nJOIN'lar\u0131n performans\u0131 \u00fczerinde hangi fakt\u00f6rler etkilidir?<\/h3>\n
\n JOIN'lar\u0131n performans\u0131 \u00fczerinde en b\u00fcy\u00fck etkiye sahip fakt\u00f6rler \u015funlard\u0131r: birle\u015ftirme ko\u015fullar\u0131nda kullan\u0131lan kolonlar\u0131n indekslenmesi, do\u011fru JOIN t\u00fcr\u00fcn\u00fcn se\u00e7ilmesi, gereksiz JOIN'lardan ka\u00e7\u0131n\u0131lmas\u0131, SELECT<\/code> ifadesinde sadece gerekli kolonlar\u0131n se\u00e7ilmesi ve veritaban\u0131 sisteminin sorgu planlay\u0131c\u0131s\u0131n\u0131n optimizasyon yetenekleri.\n<\/p>\nCROSS JOIN ve SELF JOIN'\u0131n pratik kullan\u0131m alanlar\u0131 nelerdir?<\/h3>\n
\n CROSS JOIN<\/code>, iki tablonun t\u00fcm olas\u0131 kombinasyonlar\u0131n\u0131 olu\u015fturmak i\u00e7in kullan\u0131l\u0131r (\u00f6rne\u011fin, \u00fcr\u00fcn-renk kombinasyonlar\u0131, test verisi \u00fcretimi). SELF JOIN<\/code> ise bir tablonun kendi i\u00e7indeki sat\u0131rlar\u0131 birbiriyle ili\u015fkilendirmek i\u00e7in kullan\u0131l\u0131r (\u00f6rne\u011fin, bir \u00e7al\u0131\u015fan\u0131n y\u00f6neticisini bulmak, ayn\u0131 \u015fehirdeki m\u00fc\u015fterileri listelemek). Her ikisi de daha \u00f6zel senaryolar i\u00e7in tasarlanm\u0131\u015f JOIN t\u00fcrleridir.<\/p>\n","protected":false},"excerpt":{"rendered":"\u0130li\u015fkisel veritabanlar\u0131, verileri d\u00fczenli ve y\u00f6netilebilir par\u00e7alar halinde depolamak i\u00e7in tablolar kullan\u0131r.","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1505],"tags":[],"class_list":{"0":"post-40851","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-sql-2","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nSQL JOINs: \u0130li\u015fkisel Veritabanlar\u0131nda Veri Birle\u015ftirme Sanat\u0131 - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SQL JOINs: \u0130li\u015fkisel Veritabanlar\u0131nda Veri Birle\u015ftirme Sanat\u0131\" \/>\n<meta property=\"og:description\" content=\"\u0130li\u015fkisel veritabanlar\u0131, verileri d\u00fczenli ve y\u00f6netilebilir par\u00e7alar halinde depolamak i\u00e7in tablolar kullan\u0131r.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-01T16:30:41+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"16 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"SQL JOINs: \u0130li\u015fkisel Veritabanlar\u0131nda Veri Birle\u015ftirme Sanat\u0131\",\"datePublished\":\"2026-03-01T16:30:41+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/\"},\"wordCount\":2733,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"SQL\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/#respond\"]}],\"copyrightYear\":\"2026\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/\",\"name\":\"SQL JOINs: \u0130li\u015fkisel Veritabanlar\u0131nda Veri Birle\u015ftirme Sanat\u0131 - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2026-03-01T16:30:41+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SQL JOINs: \u0130li\u015fkisel Veritabanlar\u0131nda Veri Birle\u015ftirme Sanat\u0131\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"SQL JOINs: \u0130li\u015fkisel Veritabanlar\u0131nda Veri Birle\u015ftirme Sanat\u0131 - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/","og_locale":"tr_TR","og_type":"article","og_title":"SQL JOINs: \u0130li\u015fkisel Veritabanlar\u0131nda Veri Birle\u015ftirme Sanat\u0131","og_description":"\u0130li\u015fkisel veritabanlar\u0131, verileri d\u00fczenli ve y\u00f6netilebilir par\u00e7alar halinde depolamak i\u00e7in tablolar kullan\u0131r.","og_url":"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2026-03-01T16:30:41+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"16 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"SQL JOINs: \u0130li\u015fkisel Veritabanlar\u0131nda Veri Birle\u015ftirme Sanat\u0131","datePublished":"2026-03-01T16:30:41+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/"},"wordCount":2733,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["SQL"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/#respond"]}],"copyrightYear":"2026","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/","url":"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/","name":"SQL JOINs: \u0130li\u015fkisel Veritabanlar\u0131nda Veri Birle\u015ftirme Sanat\u0131 - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2026-03-01T16:30:41+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/sql-joins-iliskisel-veritabanlarinda-veri-birlestirme-sanati\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"SQL JOINs: \u0130li\u015fkisel Veritabanlar\u0131nda Veri Birle\u015ftirme Sanat\u0131"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/40851","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=40851"}],"version-history":[{"count":0,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/40851\/revisions"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=40851"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=40851"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=40851"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}