{"id":39128,"date":"2026-02-15T02:40:41","date_gmt":"2026-02-14T23:40:41","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=39128"},"modified":"2026-02-15T02:40:41","modified_gmt":"2026-02-14T23:40:41","slug":"sqlde-between-ve-in-operatorlerini-kullanma-rehberi","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/","title":{"rendered":"SQL’de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi"},"content":{"rendered":"

<\/p>\n

SQL’de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi<\/h2>\n

SQL (Yap\u0131sal Sorgulama Dili), veritabanlar\u0131ndan bilgi almak, eklemek, g\u00fcncellemek ve silmek i\u00e7in kullan\u0131lan g\u00fc\u00e7l\u00fc bir dildir. Bu i\u015flemler s\u0131ras\u0131nda, belirli kriterlere uyan verileri filtrelemek hayati \u00f6nem ta\u015f\u0131r. SQL’deki WHERE<\/code> yan t\u00fcmcesi, bu filtreleme i\u015flemini ger\u00e7ekle\u015ftirmemizi sa\u011flar ve bu yan t\u00fcmcede kullan\u0131lan operat\u00f6rler, ko\u015fullar\u0131 tan\u0131mlamada bize yard\u0131mc\u0131 olur. Bu makalede, SQL’in en s\u0131k kullan\u0131lan ve en g\u00fc\u00e7l\u00fc filtreleme operat\u00f6rlerinden ikisi olan BETWEEN<\/code> ve IN<\/code> operat\u00f6rlerini ayr\u0131nt\u0131l\u0131 olarak inceleyece\u011fiz. Her iki operat\u00f6r\u00fcn de s\u00f6zdizimini, kullan\u0131m senaryolar\u0131n\u0131, potansiyel tuzaklar\u0131n\u0131 ve performans etkilerini \u00f6rneklerle a\u00e7\u0131klayaca\u011f\u0131z.<\/p>\n

SQL’de Operat\u00f6rler ve \u00d6nemi<\/h3>\n

SQL’deki operat\u00f6rler, sorgular\u0131m\u0131zda mant\u0131ksal veya matematiksel i\u015flemler ger\u00e7ekle\u015ftirmemizi sa\u011flayan semboller veya anahtar kelimelerdir. Kar\u015f\u0131la\u015ft\u0131rma operat\u00f6rleri (=<\/code>, ><\/code>, <<\/code>, >=<\/code>, <=<\/code>, <><\/code>, !=<\/code>), mant\u0131ksal operat\u00f6rler (AND<\/code>, OR<\/code>, NOT<\/code>), aritmetik operat\u00f6rler (+<\/code>, -<\/code>, *<\/code>, \/<\/code>) ve \u00f6zel operat\u00f6rler (LIKE<\/code>, IS NULL<\/code>, BETWEEN<\/code>, IN<\/code>) gibi \u00e7e\u015fitli kategorilerde operat\u00f6rler bulunur. Bu operat\u00f6rler, veritaban\u0131ndan istedi\u011fimiz spesifik veri setlerini \u00e7ekmek i\u00e7in sorgular\u0131m\u0131z\u0131 hassasla\u015ft\u0131rmam\u0131z\u0131 sa\u011flar. Do\u011fru operat\u00f6r\u00fcn do\u011fru yerde kullan\u0131lmas\u0131, hem sorgunun do\u011frulu\u011fu hem de performans\u0131 a\u00e7\u0131s\u0131ndan kritik \u00f6neme sahiptir. BETWEEN<\/code> ve IN<\/code> operat\u00f6rleri, \u00f6zellikle belirli bir aral\u0131ktaki veya belirli bir listedeki de\u011ferleri filtrelemek i\u00e7in tasarlanm\u0131\u015f \u00f6zel operat\u00f6rlerdir ve bu sayede daha karma\u015f\u0131k AND<\/code> veya OR<\/code> ko\u015fullar\u0131 yazmaktan bizi kurtararak sorgular\u0131n okunabilirli\u011fini ve verimlili\u011fini art\u0131r\u0131rlar.<\/p>\n

BETWEEN Operat\u00f6r\u00fc<\/h3>\n

BETWEEN<\/code> operat\u00f6r\u00fc, belirli bir aral\u0131kta yer alan de\u011ferleri se\u00e7mek i\u00e7in kullan\u0131l\u0131r. Bu aral\u0131k, ba\u015flang\u0131\u00e7 ve biti\u015f de\u011ferlerini kapsay\u0131c\u0131 (inclusive) bir \u015fekilde i\u00e7erir. Yani, belirtilen ba\u015flang\u0131\u00e7 ve biti\u015f de\u011ferleri de sonu\u00e7 k\u00fcmesine dahil edilir. BETWEEN<\/code> operat\u00f6r\u00fc genellikle say\u0131sal de\u011ferler, tarihler ve hatta baz\u0131 veritabanlar\u0131nda metin de\u011ferleri ile kullan\u0131l\u0131r.<\/p>\n

S\u00f6zdizimi ve Temel Kullan\u0131m<\/h4>\n

BETWEEN<\/code> operat\u00f6r\u00fcn\u00fcn genel s\u00f6zdizimi a\u015fa\u011f\u0131daki gibidir:<\/p>\n

SELECT kolon_adlari\nFROM tablo_adi\nWHERE kolon_adi BETWEEN baslangic_degeri AND bitis_degeri;<\/code><\/pre>\n
Burada:
\n*   kolon_adlari<\/code>: Se\u00e7mek istedi\u011finiz s\u00fctun veya s\u00fctunlar\u0131 belirtir.
\n*   tablo_adi<\/code>: Veri \u00e7ekece\u011finiz tablonun ad\u0131d\u0131r.
\n*   kolon_adi<\/code>: Filtreleme yapmak istedi\u011finiz s\u00fctundur.
\n*   baslangic_degeri<\/code>: Aral\u0131\u011f\u0131n ba\u015flang\u0131\u00e7 de\u011feridir (bu de\u011fer dahil).
\n*   bitis_degeri<\/code>: Aral\u0131\u011f\u0131n biti\u015f de\u011feridir (bu de\u011fer dahil).<\/p>\n
Say\u0131sal De\u011ferlerle Kullan\u0131m<\/h4>\n
BETWEEN<\/code> operat\u00f6r\u00fcn\u00fcn en yayg\u0131n kullan\u0131mlar\u0131ndan biri, say\u0131sal aral\u0131klar\u0131 filtrelemektir. \u00d6rne\u011fin, bir Calisanlar<\/code> (Employees) tablosunda belirli bir maa\u015f aral\u0131\u011f\u0131ndaki \u00e7al\u0131\u015fanlar\u0131 bulmak isteyebiliriz.<\/p>\n
\u00d6rnek 1: Belirli bir maa\u015f aral\u0131\u011f\u0131ndaki \u00e7al\u0131\u015fanlar\u0131 listeleme<\/strong><\/p>\n
Varsayal\u0131m ki Calisanlar<\/code> tablomuzda CalisanID<\/code>, Ad<\/code>, Soyad<\/code>, Maas<\/code> ve Yas<\/code> s\u00fctunlar\u0131 var. Maa\u015f\u0131 5000 ile 8000 aras\u0131nda olan \u00e7al\u0131\u015fanlar\u0131 bulmak i\u00e7in:<\/p>\n
SELECT CalisanID, Ad, Soyad, Maas\nFROM Calisanlar\nWHERE Maas BETWEEN 5000 AND 8000;<\/code><\/pre>\n
Bu sorgu, maa\u015f\u0131 tam olarak 5000, tam olarak 8000 veya bu iki de\u011fer aras\u0131nda olan t\u00fcm \u00e7al\u0131\u015fanlar\u0131 d\u00f6nd\u00fcrecektir. Bu, Maas >= 5000 AND Maas <= 8000<\/code> ifadesine e\u015fde\u011ferdir.<\/p>\n
Tarih ve Saat De\u011ferleriyle Kullan\u0131m<\/h4>\n
BETWEEN<\/code> operat\u00f6r\u00fc, tarih ve saat verileriyle kullan\u0131ld\u0131\u011f\u0131nda da son derece faydal\u0131d\u0131r. Belirli bir tarih aral\u0131\u011f\u0131nda ger\u00e7ekle\u015fen olaylar\u0131 veya belirli bir d\u00f6nemde i\u015fe ba\u015flayan \u00e7al\u0131\u015fanlar\u0131 bulmak i\u00e7in idealdir.<\/p>\n
\u00d6rnek 2: Belirli bir tarihler aras\u0131nda i\u015fe ba\u015flayan \u00e7al\u0131\u015fanlar\u0131 listeleme<\/strong><\/p>\n
Calisanlar<\/code> tablosunda GirisTarihi<\/code> (HireDate) ad\u0131nda bir s\u00fctun oldu\u011funu varsayal\u0131m. 2022 y\u0131l\u0131n\u0131n ilk \u00e7eyre\u011finde (1 Ocak 2022 ile 31 Mart 2022 aras\u0131) i\u015fe ba\u015flayan \u00e7al\u0131\u015fanlar\u0131 bulmak i\u00e7in:<\/p>\n
SELECT CalisanID, Ad, Soyad, GirisTarihi\nFROM Calisanlar\nWHERE GirisTarihi BETWEEN '2022-01-01' AND '2022-03-31';<\/code><\/pre>\n
Bu sorgu, 1 Ocak 2022 tarihinde veya sonras\u0131nda ve 31 Mart 2022 tarihinde veya \u00f6ncesinde i\u015fe ba\u015flayan t\u00fcm \u00e7al\u0131\u015fanlar\u0131 getirecektir. Tarih format\u0131n\u0131n veritaban\u0131 sisteminize uygun oldu\u011fundan emin olun (\u00f6rne\u011fin, PostgreSQL'de YYYY-MM-DD<\/code>, SQL Server'da YYYYMMDD<\/code> veya YYYY-MM-DD<\/code> genellikle kabul edilir).<\/p>\n
Saat bilgisi i\u00e7eren DATETIME<\/code> veya TIMESTAMP<\/code> s\u00fctunlar\u0131 ile \u00e7al\u0131\u015f\u0131rken dikkatli olunmal\u0131d\u0131r. E\u011fer GirisTarihi<\/code> s\u00fctunu saat bilgisi i\u00e7eriyorsa ve siz sadece tarih baz\u0131nda filtreleme yap\u0131yorsan\u0131z, biti\u015f tarihi i\u00e7in 2022-03-31 23:59:59<\/code> gibi bir de\u011fer kullanman\u0131z gerekebilir, aksi takdirde 31 Mart'\u0131n sadece ilk saniyesini kapsars\u0131n\u0131z.<\/p>\n
\u00d6rnek 3: Saat bilgisi i\u00e7eren bir aral\u0131kta filtreleme<\/strong><\/p>\n
SELECT CalisanID, Ad, Soyad, GirisTarihi\nFROM Calisanlar\nWHERE GirisTarihi BETWEEN '2022-03-15 09:00:00' AND '2022-03-15 17:00:00';<\/code><\/pre>\n
Bu sorgu, 15 Mart 2022 tarihinde sabah 9 ile ak\u015fam 5 aras\u0131nda i\u015fe ba\u015flayan \u00e7al\u0131\u015fanlar\u0131 getirecektir.<\/p>\n
Metin De\u011ferleriyle Kullan\u0131m<\/h4>\n
Baz\u0131 veritaban\u0131 sistemlerinde (\u00f6zellikle alfabetik s\u0131ralamay\u0131 destekleyenlerde), BETWEEN<\/code> operat\u00f6r\u00fc metin de\u011ferleriyle de kullan\u0131labilir. Bu durumda, metin de\u011ferlerinin alfabetik s\u0131ras\u0131 dikkate al\u0131n\u0131r.<\/p>\n
\u00d6rnek 4: Belirli bir harf aral\u0131\u011f\u0131ndaki soyadlar\u0131 listeleme<\/strong><\/p>\n
Soyad\u0131 'A' ile 'M' harfleri aras\u0131nda ba\u015flayan \u00e7al\u0131\u015fanlar\u0131 bulmak i\u00e7in:<\/p>\n
SELECT CalisanID, Ad, Soyad\nFROM Calisanlar\nWHERE Soyad BETWEEN 'A' AND 'Mzzzzz'; -- veya 'N' (veritaban\u0131na g\u00f6re de\u011fi\u015febilir)<\/code><\/pre>\n
Burada dikkat edilmesi gereken nokta, metin s\u0131ralamas\u0131n\u0131n veritaban\u0131 ve karakter seti ayarlar\u0131na ba\u011fl\u0131 olmas\u0131d\u0131r. \u00d6rne\u011fin, BETWEEN 'A' AND 'M'<\/code> sadece 'A' ile ba\u015flayanlar\u0131 ve 'M' ile ba\u015flayanlar\u0131 kapsamaz, ayn\u0131 zamanda 'M' harfinden sonra gelen ancak 'M' harfiyle ba\u015flayan kelimelerin alfabetik olarak sonuna kadar gitmeyen kelimeleri de kapsar. Genellikle, bir harf aral\u0131\u011f\u0131n\u0131 kapsamak i\u00e7in biti\u015f de\u011ferini o harfin sonuna kadar gidecek \u015fekilde (\u00f6rne\u011fin 'Mzzzzz') veya bir sonraki harfin ba\u015flang\u0131c\u0131 olarak (\u00f6rne\u011fin 'N') belirtmek daha g\u00fcvenli olabilir. Ancak bu kullan\u0131m, \u00f6zellikle b\u00fcy\u00fck\/k\u00fc\u00e7\u00fck harf duyarl\u0131l\u0131\u011f\u0131 ve farkl\u0131 karakter setleri nedeniyle karma\u015f\u0131kla\u015fabilir ve genellikle LIKE<\/code> operat\u00f6r\u00fc (WHERE Soyad LIKE 'A%' OR Soyad LIKE 'B%' ...<\/code>) veya SUBSTRING<\/code> ile BETWEEN<\/code> kombinasyonu daha net sonu\u00e7lar verebilir.<\/p>\n
NOT BETWEEN ile Tersine \u00c7evirme<\/h4>\n
NOT<\/code> anahtar kelimesi, BETWEEN<\/code> operat\u00f6r\u00fcn\u00fcn ko\u015fulunu tersine \u00e7evirmek i\u00e7in kullan\u0131labilir. NOT BETWEEN<\/code> operat\u00f6r\u00fc, belirtilen aral\u0131\u011f\u0131n d\u0131\u015f\u0131nda kalan de\u011ferleri se\u00e7er.<\/p>\n
\u00d6rnek 5: Maa\u015f\u0131 5000 ile 8000 aras\u0131nda OLMAYAN \u00e7al\u0131\u015fanlar\u0131 listeleme<\/strong><\/p>\n
SELECT CalisanID, Ad, Soyad, Maas\nFROM Calisanlar\nWHERE Maas NOT BETWEEN 5000 AND 8000;<\/code><\/pre>\n
Bu sorgu, maa\u015f\u0131 5000'den az olan veya 8000'den fazla olan t\u00fcm \u00e7al\u0131\u015fanlar\u0131 d\u00f6nd\u00fcrecektir. Bu, Maas < 5000 OR Maas > 8000<\/code> ifadesine e\u015fde\u011ferdir.<\/p>\n
BETWEEN Kullan\u0131m\u0131nda Dikkat Edilmesi Gerekenler<\/h4>\n
*   S\u0131n\u0131rlay\u0131c\u0131lar\u0131n Dahil Edilmesi (Inclusivity):<\/strong> BETWEEN<\/code> operat\u00f6r\u00fc, ba\u015flang\u0131\u00e7 ve biti\u015f de\u011ferlerini kapsay\u0131c\u0131d\u0131r. Bu, \u00e7o\u011fu zaman istenen bir davran\u0131\u015ft\u0131r, ancak bazen yanl\u0131\u015f anla\u015f\u0131labilir. E\u011fer sadece ba\u015flang\u0131\u00e7 ve biti\u015f de\u011ferleri aras\u0131ndaki de\u011ferleri (bu de\u011ferler hari\u00e7) istiyorsan\u0131z, ><\/code> ve <<\/code> operat\u00f6rlerini kullanman\u0131z gerekir. \u00d6rne\u011fin, Maas > 5000 AND Maas < 8000<\/code>.
\n*   Veri Tipi Uyumlulu\u011fu:<\/strong> BETWEEN<\/code> operat\u00f6r\u00fcn\u00fc kullan\u0131rken, kar\u015f\u0131la\u015ft\u0131rd\u0131\u011f\u0131n\u0131z s\u00fctunun veri tipi ile ba\u015flang\u0131\u00e7 ve biti\u015f de\u011ferlerinin veri tiplerinin uyumlu oldu\u011fundan emin olun. Aksi takdirde, veritaban\u0131 \u00f6rt\u00fcl\u00fc bir d\u00f6n\u00fc\u015f\u00fcm yapmaya \u00e7al\u0131\u015fabilir, bu da performans sorunlar\u0131na veya beklenmedik sonu\u00e7lara yol a\u00e7abilir. \u00d6rne\u011fin, metin olarak depolanm\u0131\u015f say\u0131sal de\u011ferleri BETWEEN<\/code> ile kar\u015f\u0131la\u015ft\u0131rmak beklenmedik sonu\u00e7lar verebilir.
\n*   NULL De\u011ferler:<\/strong> BETWEEN<\/code> operat\u00f6r\u00fc, NULL<\/code> de\u011ferlerle kar\u015f\u0131la\u015ft\u0131r\u0131ld\u0131\u011f\u0131nda UNKNOWN<\/code> (bilinmeyen) bir sonu\u00e7 d\u00f6nd\u00fcr\u00fcr. E\u011fer filtrelenen s\u00fctunda NULL<\/code> de\u011ferler varsa, bu sat\u0131rlar BETWEEN<\/code> veya NOT BETWEEN<\/code> ko\u015fullar\u0131 taraf\u0131ndan d\u00f6nd\u00fcr\u00fclmez. NULL<\/code> de\u011ferleri de dahil etmek isterseniz, OR kolon_adi IS NULL<\/code> gibi ek bir ko\u015ful eklemeniz gerekir.
\n*   Performans Etkisi:<\/strong> BETWEEN<\/code> operat\u00f6r\u00fc, genellikle indekslenmi\u015f s\u00fctunlarda kullan\u0131ld\u0131\u011f\u0131nda \u00e7ok etkilidir. Veritaban\u0131 y\u00f6netim sistemleri (DBMS), indeksleri kullanarak aral\u0131ktaki verileri h\u0131zl\u0131 bir \u015fekilde bulabilir. Bu nedenle, s\u0131k\u00e7a aral\u0131k sorgular\u0131 yapt\u0131\u011f\u0131n\u0131z s\u00fctunlara indeks eklemeyi d\u00fc\u015f\u00fcnebilirsiniz.<\/p>\n
IN Operat\u00f6r\u00fc<\/h3>\n
IN<\/code> operat\u00f6r\u00fc, bir s\u00fctunun de\u011ferinin, belirtilen bir de\u011fer listesi i\u00e7inde olup olmad\u0131\u011f\u0131n\u0131 kontrol etmek i\u00e7in kullan\u0131l\u0131r. Bu, bir s\u00fctunu birden fazla de\u011ferle OR<\/code> ko\u015fullar\u0131 kullanarak kar\u015f\u0131la\u015ft\u0131rmaktan \u00e7ok daha k\u0131sa ve okunabilir bir yol sunar.<\/p>\n
S\u00f6zdizimi ve Temel Kullan\u0131m<\/h4>\n
IN<\/code> operat\u00f6r\u00fcn\u00fcn genel s\u00f6zdizimi a\u015fa\u011f\u0131daki gibidir:<\/p>\n
SELECT kolon_adlari\nFROM tablo_adi\nWHERE kolon_adi IN (deger1, deger2, deger3, ...);<\/code><\/pre>\n
Burada:
\n*   kolon_adlari<\/code>: Se\u00e7mek istedi\u011finiz s\u00fctun veya s\u00fctunlar\u0131 belirtir.
\n*   tablo_adi<\/code>: Veri \u00e7ekece\u011finiz tablonun ad\u0131d\u0131r.
\n*   kolon_adi<\/code>: Filtreleme yapmak istedi\u011finiz s\u00fctundur.
\n*   deger1, deger2, deger3, ...<\/code>: S\u00fctunun de\u011ferinin e\u015fle\u015fmesini istedi\u011finiz de\u011fer listesidir.<\/p>\n
Tek De\u011fer Listesiyle Kullan\u0131m<\/h4>\n
IN<\/code> operat\u00f6r\u00fc en basit haliyle, sabit bir de\u011fer listesiyle kullan\u0131l\u0131r.<\/p>\n
\u00d6rnek 6: Belirli departmanlardaki \u00e7al\u0131\u015fanlar\u0131 listeleme<\/strong><\/p>\n
Calisanlar<\/code> tablosunda DepartmanID<\/code> ad\u0131nda bir s\u00fctun oldu\u011funu varsayal\u0131m. Departman ID'si 101, 103 veya 105 olan \u00e7al\u0131\u015fanlar\u0131 bulmak i\u00e7in:<\/p>\n
SELECT CalisanID, Ad, Soyad, DepartmanID\nFROM Calisanlar\nWHERE DepartmanID IN (101, 103, 105);<\/code><\/pre>\n
Bu sorgu, DepartmanID = 101 OR DepartmanID = 103 OR DepartmanID = 105<\/code> ifadesine e\u015fde\u011ferdir, ancak \u00e7ok daha k\u0131sa ve okunabilirdir.<\/p>\n
IN<\/code> operat\u00f6r\u00fc, say\u0131sal, metin veya tarih\/saat gibi farkl\u0131 veri tipleriyle kullan\u0131labilir, yeter ki listedeki de\u011ferler ve s\u00fctunun veri tipi uyumlu olsun.<\/p>\n
\u00d6rnek 7: Belirli isimlere sahip \u00e7al\u0131\u015fanlar\u0131 listeleme<\/strong><\/p>\n
SELECT CalisanID, Ad, Soyad\nFROM Calisanlar\nWHERE Ad IN ('Ay\u015fe', 'Mehmet', 'Zeynep');<\/code><\/pre>\n
Alt Sorgularla Kullan\u0131m<\/h4>\n
IN<\/code> operat\u00f6r\u00fcn\u00fcn g\u00fcc\u00fc, de\u011fer listesinin bir alt sorgu (subquery) taraf\u0131ndan dinamik olarak olu\u015fturulabildi\u011fi durumlarda ortaya \u00e7\u0131kar. Bu, bir tablodaki verileri ba\u015fka bir tablodaki verilere g\u00f6re filtrelemek i\u00e7in son derece kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n
\u00d6rnek 8: Belirli bir departmandaki (Departmanlar tablosundan gelen) \u00e7al\u0131\u015fanlar\u0131 listeleme<\/strong><\/p>\n
Varsayal\u0131m ki Departmanlar<\/code> ad\u0131nda bir tablomuz var ve bu tabloda DepartmanID<\/code> ve DepartmanAdi<\/code> s\u00fctunlar\u0131 bulunuyor. \"Sat\u0131\u015f\" veya \"Pazarlama\" departmanlar\u0131nda \u00e7al\u0131\u015fanlar\u0131 bulmak istiyoruz.<\/p>\n
SELECT CalisanID, Ad, Soyad, DepartmanID\nFROM Calisanlar\nWHERE DepartmanID IN (SELECT DepartmanID FROM Departmanlar WHERE DepartmanAdi IN ('Sat\u0131\u015f', 'Pazarlama'));<\/code><\/pre>\n
Bu sorgu \u00f6nce Departmanlar<\/code> tablosundan \"Sat\u0131\u015f\" ve \"Pazarlama\" departmanlar\u0131n\u0131n ID'lerini \u00e7eker, ard\u0131ndan bu ID'leri kullanarak Calisanlar<\/code> tablosunu filtreler. Bu, iki tabloyu JOIN<\/code> yapmadan da benzer bir sonu\u00e7 elde etmenin bir yoludur.<\/p>\n
NOT IN ile Tersine \u00c7evirme<\/h4>\n
NOT<\/code> anahtar kelimesi, IN<\/code> operat\u00f6r\u00fcn\u00fcn ko\u015fulunu tersine \u00e7evirmek i\u00e7in kullan\u0131labilir. NOT IN<\/code> operat\u00f6r\u00fc, belirtilen de\u011fer listesinde yer almayan de\u011ferleri se\u00e7er.<\/p>\n
\u00d6rnek 9: Departman ID'si 101, 103 veya 105 OLMAYAN \u00e7al\u0131\u015fanlar\u0131 listeleme<\/strong><\/p>\n
SELECT CalisanID, Ad, Soyad, DepartmanID\nFROM Calisanlar\nWHERE DepartmanID NOT IN (101, 103, 105);<\/code><\/pre>\n
Bu sorgu, departman ID'si 101, 103 veya 105 d\u0131\u015f\u0131ndaki t\u00fcm \u00e7al\u0131\u015fanlar\u0131 d\u00f6nd\u00fcrecektir.<\/p>\n
IN Kullan\u0131m\u0131nda Dikkat Edilmesi Gerekenler<\/h4>\n
*   Liste Boyutu ve Performans:<\/strong> IN<\/code> operat\u00f6r\u00fc, k\u00fc\u00e7\u00fck ve sabit de\u011fer listeleri i\u00e7in \u00e7ok etkilidir. Ancak, listedeki \u00f6\u011fe say\u0131s\u0131 \u00e7ok fazla oldu\u011funda (y\u00fczlerce veya binlerce), sorgu performans\u0131 d\u00fc\u015febilir. Bu t\u00fcr durumlarda, \u00f6zellikle de\u011fer listesi ba\u015fka bir tablodan geliyorsa, JOIN<\/code> veya EXISTS<\/code> operat\u00f6rlerini kullanmak daha iyi bir alternatif olabilir.
\n*   NULL De\u011ferler ve IN Operat\u00f6r\u00fc:<\/strong> IN<\/code> operat\u00f6r\u00fc ile NULL<\/code> de\u011ferlerin kullan\u0131m\u0131 \u00f6zel dikkat gerektirir.
\n    *   IN<\/code> listesinde NULL<\/code> olmas\u0131:<\/strong> E\u011fer IN<\/code> listesinde bir NULL<\/code> de\u011feri varsa (\u00f6rne\u011fin, IN (1, 2, NULL)<\/code>), ve s\u00fctunun de\u011feri NULL<\/code> de\u011filse, sorgu normal \u00e7al\u0131\u015f\u0131r. Ancak s\u00fctunun de\u011feri de NULL<\/code> ise, NULL IN (1, 2, NULL)<\/code> ifadesi UNKNOWN<\/code> d\u00f6nd\u00fcr\u00fcr ve bu sat\u0131r sonu\u00e7 k\u00fcmesine dahil edilmez.
\n    *   NOT IN<\/code> listesinde NULL<\/code> olmas\u0131:<\/strong> Bu, IN<\/code> operat\u00f6r\u00fcn\u00fcn en \u00f6nemli potansiyel tuzaklar\u0131ndan biridir. E\u011fer NOT IN<\/code> listesinde bir NULL<\/code> de\u011feri varsa (\u00f6rne\u011fin, NOT IN (1, 2, NULL)<\/code>), sorgu genellikle hi\u00e7bir sonu\u00e7 d\u00f6nd\u00fcrmez! Bunun nedeni, NOT IN (deger1, deger2, ..., NULL)<\/code> ifadesinin asl\u0131nda kolon != deger1 AND kolon != deger2 AND ... AND kolon != NULL<\/code> olarak yorumlanmas\u0131d\u0131r. SQL'de herhangi_bir_deger != NULL<\/code> ifadesi her zaman UNKNOWN<\/code> d\u00f6nd\u00fcr\u00fcr. UNKNOWN<\/code> ile yap\u0131lan AND<\/code> i\u015flemleri de UNKNOWN<\/code> d\u00f6nd\u00fcrece\u011fi i\u00e7in, t\u00fcm ko\u015ful UNKNOWN<\/code> olur ve hi\u00e7bir sat\u0131r e\u015fle\u015fmez. Bu durumdan ka\u00e7\u0131nmak i\u00e7in, NOT IN<\/code> ile kullan\u0131lan alt sorgular\u0131n NULL<\/code> de\u011fer d\u00f6nd\u00fcrmedi\u011finden emin olun veya NOT EXISTS<\/code> kullanmay\u0131 tercih edin.
\n*   Veri Tipi Uyumlulu\u011fu:<\/strong> BETWEEN<\/code> operat\u00f6r\u00fcnde oldu\u011fu gibi, IN<\/code> operat\u00f6r\u00fcnde de s\u00fctunun veri tipi ile listedeki de\u011ferlerin veri tipi uyumlu olmal\u0131d\u0131r.<\/p>\n
BETWEEN ve IN Operat\u00f6rlerinin Kar\u015f\u0131la\u015ft\u0131r\u0131lmas\u0131<\/h3>\n
BETWEEN<\/code> ve IN<\/code> operat\u00f6rleri, her ikisi de WHERE<\/code> yan t\u00fcmcesinde filtreleme i\u00e7in kullan\u0131lsa da, farkl\u0131 senaryolar i\u00e7in optimize edilmi\u015flerdir.<\/p>\n
Kullan\u0131m Senaryolar\u0131<\/h4>\n
*   BETWEEN:<\/strong> Belirli bir aral\u0131kta (minimum ve maksimum de\u011ferler aras\u0131nda) yer alan de\u011ferleri se\u00e7mek i\u00e7in idealdir. Bu aral\u0131k genellikle s\u00fcrekli bir say\u0131sal dizi, bir tarih aral\u0131\u011f\u0131 veya alfabetik bir metin aral\u0131\u011f\u0131d\u0131r. \u00d6rne\u011fin, ya\u015f aral\u0131\u011f\u0131, maa\u015f aral\u0131\u011f\u0131, tarih aral\u0131\u011f\u0131 gibi durumlarda tercih edilir.
\n*   IN:<\/strong> Belirli bir de\u011fer listesinden (kesikli de\u011ferler k\u00fcmesi) e\u015fle\u015fen de\u011ferleri se\u00e7mek i\u00e7in kullan\u0131l\u0131r. Bu liste sabit olabilir veya bir alt sorgu taraf\u0131ndan dinamik olarak olu\u015fturulabilir. \u00d6rne\u011fin, belirli departmanlar, belirli \u00fcr\u00fcn kodlar\u0131 veya belirli kullan\u0131c\u0131 ID'leri gibi durumlarda tercih edilir.<\/p>\n
Performans Farkl\u0131l\u0131klar\u0131<\/h4>\n
*   BETWEEN:<\/strong> Genellikle indeksli s\u00fctunlarda \u00e7ok iyi performans g\u00f6sterir. Veritaban\u0131, indeksleri kullanarak aral\u0131\u011f\u0131n ba\u015flang\u0131c\u0131n\u0131 ve sonunu h\u0131zl\u0131ca bulabilir ve bu aral\u0131ktaki t\u00fcm verileri verimli bir \u015fekilde \u00e7ekebilir.
\n*   IN:<\/strong>
\n    *   K\u00fc\u00e7\u00fck, sabit listelerle kullan\u0131ld\u0131\u011f\u0131nda performans\u0131 iyidir. Veritaban\u0131, listeyi bir dizi OR<\/code> ko\u015fuluna \u00e7evirebilir ve her bir de\u011feri h\u0131zl\u0131ca kontrol edebilir.
\n    *   \u00c7ok b\u00fcy\u00fck listelerle kullan\u0131ld\u0131\u011f\u0131nda performans d\u00fc\u015febilir. Baz\u0131 veritabanlar\u0131 bu durumu optimize etse de, liste boyutu artt\u0131k\u00e7a maliyet artar.
\n    *   Alt sorgularla kullan\u0131ld\u0131\u011f\u0131nda, alt sorgunun kendisinin performans\u0131 \u00f6nemlidir. Alt sorgu verimli \u00e7al\u0131\u015f\u0131yorsa, IN<\/code> de verimli olabilir. Ancak, alt sorgunun \u00e7ok say\u0131da sat\u0131r d\u00f6nd\u00fcrmesi veya her ana sorgu sat\u0131r\u0131 i\u00e7in tekrar \u00e7al\u0131\u015fmas\u0131 (korelasyonlu alt sorgularda) performans\u0131 etkileyebilir. B\u00fcy\u00fck alt sorgu sonu\u00e7lar\u0131 i\u00e7in JOIN<\/code> veya EXISTS<\/code> genellikle daha iyi performans sunabilir.<\/p>\n
Okunabilirlik ve Bak\u0131m<\/h4>\n
*   Her iki operat\u00f6r de, uzun AND<\/code> veya OR<\/code> zincirleri yerine kullan\u0131ld\u0131\u011f\u0131nda sorgunun okunabilirli\u011fini \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131r\u0131r.
\n*   BETWEEN<\/code>, bir aral\u0131\u011f\u0131 tek bir ifadeyle tan\u0131mlad\u0131\u011f\u0131 i\u00e7in \u00e7ok sezgiseldir.
\n*   IN<\/code>, birden fazla de\u011feri tek bir liste i\u00e7inde gruplad\u0131\u011f\u0131 i\u00e7in benzer \u015fekilde sezgiseldir.
\n*   Bak\u0131m a\u00e7\u0131s\u0131ndan, IN<\/code> listesine yeni de\u011ferler eklemek veya \u00e7\u0131karmak, OR<\/code> ko\u015fullar\u0131 zincirini de\u011fi\u015ftirmekten daha kolayd\u0131r.<\/p>\n
Geli\u015fmi\u015f Kullan\u0131m Senaryolar\u0131 ve \u0130pu\u00e7lar\u0131<\/h3>\n
BETWEEN<\/code> ve IN<\/code> operat\u00f6rlerini daha karma\u015f\u0131k sorgularda di\u011fer SQL yap\u0131lar\u0131yla birle\u015ftirmek, daha g\u00fc\u00e7l\u00fc ve esnek filtreleme yetenekleri sunar.<\/p>\n
Birden Fazla Ko\u015fulla Kullan\u0131m<\/h4>\n
Bu operat\u00f6rleri AND<\/code>, OR<\/code> ve NOT<\/code> gibi mant\u0131ksal operat\u00f6rlerle birle\u015ftirerek daha spesifik filtreler olu\u015fturabilirsiniz.<\/p>\n
\u00d6rnek 10: Belirli bir departmandaki ve belirli bir ya\u015f aral\u0131\u011f\u0131ndaki \u00e7al\u0131\u015fanlar\u0131 listeleme<\/strong><\/p>\n
SELECT CalisanID, Ad, Soyad, DepartmanID, Yas\nFROM Calisanlar\nWHERE DepartmanID IN (101, 105) AND Yas BETWEEN 25 AND 40;<\/code><\/pre>\n
Bu sorgu, hem departman ID'si 101 veya 105 olan hem de ya\u015f\u0131 25 ile 40 aras\u0131nda olan \u00e7al\u0131\u015fanlar\u0131 getirecektir.<\/p>\n
JOIN \u0130\u015flemleriyle Birlikte Kullan\u0131m<\/h4>\n
BETWEEN<\/code> ve IN<\/code> operat\u00f6rleri, JOIN<\/code> i\u015flemleriyle birle\u015ftirilerek birden fazla tablodan gelen verileri filtrelemek i\u00e7in kullan\u0131labilir.<\/p>\n
\u00d6rnek 11: Belirli bir b\u00f6lgedeki (B\u00f6lgeler tablosundan) ve belirli bir maa\u015f aral\u0131\u011f\u0131ndaki \u00e7al\u0131\u015fanlar\u0131 listeleme<\/strong><\/p>\n
Varsayal\u0131m ki Departmanlar<\/code> tablosunda BolgeID<\/code> (RegionID) ve B\u00f6lgeler<\/code> tablosunda BolgeID<\/code> ve BolgeAdi<\/code> s\u00fctunlar\u0131 var. \"Kuzey\" veya \"Do\u011fu\" b\u00f6lgelerindeki ve maa\u015f\u0131 6000'den fazla olan \u00e7al\u0131\u015fanlar\u0131 bulmak i\u00e7in:<\/p>\n
SELECT C.Ad, C.Soyad, C.Maas, D.DepartmanAdi, B.BolgeAdi\nFROM Calisanlar C\nJOIN Departmanlar D ON C.DepartmanID = D.DepartmanID\nJOIN Bolgeler B ON D.BolgeID = B.BolgeID\nWHERE B.BolgeAdi IN ('Kuzey', 'Do\u011fu') AND C.Maas > 6000;<\/code><\/pre>\n
Bu \u00f6rnekte, IN<\/code> operat\u00f6r\u00fc BolgeAdi<\/code> s\u00fctununu filtrelerken, Maas > 6000<\/code> ko\u015fulu da uygulanm\u0131\u015ft\u0131r.<\/p>\n
Performans\u0131 Optimize Etme \u0130pu\u00e7lar\u0131<\/h4>\n
*   \u0130ndeksleme:<\/strong> BETWEEN<\/code> ve IN<\/code> operat\u00f6rlerinin kullan\u0131ld\u0131\u011f\u0131 s\u00fctunlara indeks eklemek, sorgu performans\u0131n\u0131 \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131rabilir. \u00d6zellikle WHERE<\/code> yan t\u00fcmcesinde s\u0131k\u00e7a kullan\u0131lan s\u00fctunlar i\u00e7in indeksler hayati \u00f6neme sahiptir.
\n*   IN<\/code> yerine EXISTS<\/code> veya JOIN<\/code>:<\/strong> E\u011fer IN<\/code> operat\u00f6r\u00fcn\u00fc b\u00fcy\u00fck bir alt sorgu ile kullan\u0131yorsan\u0131z, \u00f6zellikle NOT IN<\/code> durumunda ve alt sorgu NULL<\/code> de\u011ferler d\u00f6nd\u00fcrebiliyorsa, EXISTS<\/code> veya LEFT JOIN<\/code> ile IS NULL<\/code> kombinasyonunu de\u011ferlendirin.
\n    *   EXISTS<\/code>:<\/strong> Bir alt sorgunun en az bir sat\u0131r d\u00f6nd\u00fcr\u00fcp d\u00f6nd\u00fcrmedi\u011fini kontrol eder. Performans a\u00e7\u0131s\u0131ndan genellikle IN<\/code>'den daha verimlidir, \u00e7\u00fcnk\u00fc alt sorgu ilk e\u015fle\u015fmeyi buldu\u011funda durabilir.
\n    *   JOIN<\/code>:<\/strong> \u0130ki tabloyu birle\u015ftirerek filtreleme yapmak, IN<\/code> ile alt sorgu kullanmaktan daha performansl\u0131 olabilir, \u00f6zellikle veritaban\u0131 optimizasyonu iyi ayarlanm\u0131\u015fsa.
\n*   Statik Listeleri K\u0131sa Tutun:<\/strong> IN<\/code> operat\u00f6r\u00fc i\u00e7in statik de\u011fer listeleri kullan\u0131yorsan\u0131z, bu listeleri m\u00fcmk\u00fcn oldu\u011funca k\u0131sa tutmaya \u00e7al\u0131\u015f\u0131n. \u00c7ok uzun listeler, sorgu planlay\u0131c\u0131s\u0131 i\u00e7in zorluklar yaratabilir.
\n*   Veri Tipi Tutarl\u0131l\u0131\u011f\u0131:<\/strong> Sorgular\u0131n\u0131zda veri tipi d\u00f6n\u00fc\u015f\u00fcmlerinden ka\u00e7\u0131nmak i\u00e7in her zaman s\u00fctunlar\u0131n ve kar\u015f\u0131la\u015ft\u0131r\u0131lan de\u011ferlerin veri tiplerinin uyumlu oldu\u011fundan emin olun. \u00d6rt\u00fcl\u00fc d\u00f6n\u00fc\u015f\u00fcmler performans\u0131 olumsuz etkileyebilir.<\/p>\n
Yayg\u0131n Hatalar ve \u00c7\u00f6z\u00fcmleri<\/h3>\n
1.  BETWEEN<\/code> ve Tarih\/Saat Verileriyle Yanl\u0131\u015f Aral\u0131k Belirleme:<\/strong>
\n    *   Hata:<\/strong> GirisTarihi BETWEEN '2022-01-01' AND '2022-01-31'<\/code> kullan\u0131ld\u0131\u011f\u0131nda, GirisTarihi<\/code> bir DATETIME<\/code> veya TIMESTAMP<\/code> s\u00fctunuysa ve saat bilgisi i\u00e7eriyorsa, 31 Ocak'\u0131n sadece gece yar\u0131s\u0131 (00:00:00) dahil edilir. 31 Ocak'taki di\u011fer saatlerdeki kay\u0131tlar atlan\u0131r.
\n    *   \u00c7\u00f6z\u00fcm:<\/strong> Biti\u015f tarihine g\u00fcn\u00fcn son saatini ekleyin: GirisTarihi BETWEEN '2022-01-01 00:00:00' AND '2022-01-31 23:59:59.999'<\/code> (veritaban\u0131n\u0131n hassasiyetine g\u00f6re). Veya sadece tarih k\u0131sm\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131ran fonksiyonlar kullan\u0131n (\u00f6rne\u011fin, SQL Server'da CAST(GirisTarihi AS DATE)<\/code> veya PostgreSQL'de GirisTarihi::date<\/code>).
\n    *   Alternatif \u00c7\u00f6z\u00fcm:<\/strong> GirisTarihi >= '2022-01-01' AND GirisTarihi < '2022-02-01'<\/code> kullanmak, 31 Ocak'\u0131n t\u00fcm\u00fcn\u00fc kapsayacak ve saat hassasiyeti sorununu ortadan kald\u0131racakt\u0131r. Bu genellikle tarih aral\u0131klar\u0131 i\u00e7in daha g\u00fcvenli bir yakla\u015f\u0131md\u0131r.<\/p>\n
2.  NOT IN<\/code> ile Alt Sorgularda NULL<\/code> De\u011ferler:<\/strong>
\n    *   Hata:<\/strong> WHERE CalisanID NOT IN (SELECT YoneticiID FROM Calisanlar WHERE YoneticiID IS NOT NULL)<\/code> gibi bir sorguda, e\u011fer alt sorgu NULL<\/code> de\u011ferler d\u00f6nd\u00fcr\u00fcrse (ki bu \u00f6rnekte IS NOT NULL<\/code> ile engellenmi\u015f), ana sorgu hi\u00e7bir sonu\u00e7 d\u00f6nd\u00fcrmeyebilir.
\n    *   \u00c7\u00f6z\u00fcm:<\/strong> Alt sorgunun NULL<\/code> de\u011fer d\u00f6nd\u00fcrmedi\u011finden emin olun (\u00f6rne\u011fin, WHERE YoneticiID IS NOT NULL<\/code> ekleyerek). Veya NOT EXISTS<\/code> kullan\u0131n:<\/p>\n
SELECT CalisanID, Ad, Soyad\n        FROM Calisanlar C\n        WHERE NOT EXISTS (SELECT 1 FROM Yoneticiler Y WHERE C.CalisanID = Y.YoneticiID);<\/code><\/pre>\n
        Bu, NOT IN<\/code>'in NULL<\/code> tuza\u011f\u0131ndan ka\u00e7\u0131nmak i\u00e7in g\u00fcvenli bir alternatiftir.<\/p>\n
3.  B\u00fcy\u00fck IN<\/code> Listeleriyle Performans Sorunlar\u0131:<\/strong>
\n    *   Hata:<\/strong> WHERE UrunID IN (1, 2, ..., 10000)<\/code> gibi \u00e7ok uzun bir statik liste veya \u00e7ok say\u0131da sat\u0131r d\u00f6nd\u00fcren bir alt sorgu kullanmak.
\n    *   \u00c7\u00f6z\u00fcm:<\/strong> E\u011fer liste ba\u015fka bir tablodan geliyorsa, JOIN<\/code> kullanmay\u0131 d\u00fc\u015f\u00fcn\u00fcn:<\/p>\n
SELECT U.UrunAdi, U.Fiyat\n        FROM Urunler U\n        JOIN SepetDetaylari SD ON U.UrunID = SD.UrunID\n        WHERE SD.SepetID = 123;<\/code><\/pre>\n
        Veya EXISTS<\/code> kullan\u0131n:<\/p>\n
SELECT U.UrunAdi, U.Fiyat\n        FROM Urunler U\n        WHERE EXISTS (SELECT 1 FROM SepetDetaylari SD WHERE SD.UrunID = U.UrunID AND SD.SepetID = 123);<\/code><\/pre>\n
Sonu\u00e7<\/h3>\n
BETWEEN<\/code> ve IN<\/code> operat\u00f6rleri, SQL'de veri filtreleme yeteneklerimizi b\u00fcy\u00fck \u00f6l\u00e7\u00fcde art\u0131ran g\u00fc\u00e7l\u00fc ve esnek ara\u00e7lard\u0131r. BETWEEN<\/code>, s\u00fcrekli aral\u0131klar i\u00e7in m\u00fckemmel bir se\u00e7imken, IN<\/code>, kesikli de\u011fer listeleri veya alt sorgulardan gelen dinamik listeler i\u00e7in vazge\u00e7ilmezdir. Her iki operat\u00f6r de sorgular\u0131n okunabilirli\u011fini art\u0131r\u0131r ve do\u011fru kullan\u0131ld\u0131\u011f\u0131nda performansa katk\u0131da bulunur.<\/p>\n
Ancak, her ara\u00e7ta oldu\u011fu gibi, bu operat\u00f6rlerin de kendine \u00f6zg\u00fc kullan\u0131m kurallar\u0131 ve potansiyel tuzaklar\u0131 vard\u0131r. \u00d6zellikle tarih\/saat verileriyle BETWEEN<\/code> kullan\u0131rken aral\u0131klar\u0131n kapsam\u0131n\u0131 do\u011fru anlamak ve NOT IN<\/code> operat\u00f6r\u00fcn\u00fc alt sorgularla kullan\u0131rken NULL<\/code> de\u011ferlerin etkilerini g\u00f6z \u00f6n\u00fcnde bulundurmak kritik \u00f6neme sahiptir. \u0130ndeksleme, uygun alternatif operat\u00f6r se\u00e7imi (JOIN<\/code>, EXISTS<\/code>) ve veri tipi tutarl\u0131l\u0131\u011f\u0131 gibi en iyi uygulamalar\u0131 takip ederek, SQL sorgular\u0131n\u0131z\u0131n hem do\u011fru hem de performansl\u0131 olmas\u0131n\u0131 sa\u011flayabilirsiniz. Bu makalede ele al\u0131nan bilgilerle, SQL'de BETWEEN<\/code> ve IN<\/code> operat\u00f6rlerini daha bilin\u00e7li ve etkili bir \u015fekilde kullanabileceksiniz.<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"SQL’de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi\nSQL (Yap\u0131sal Sorgulama Dili), veritabanlar\u0131ndan bilgi almak, eklemek, g\u00fcncellemek ve silmek","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-39128","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'de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi - 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\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SQL'de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi\" \/>\n<meta property=\"og:description\" content=\"SQL'de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi SQL (Yap\u0131sal Sorgulama Dili), veritabanlar\u0131ndan bilgi almak, eklemek, g\u00fcncellemek ve silmek\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2026-02-14T23:40: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=\"5 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"SQL’de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi\",\"datePublished\":\"2026-02-14T23:40:41+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/\"},\"wordCount\":2915,\"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\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/#respond\"]}],\"copyrightYear\":\"2026\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/\",\"name\":\"SQL'de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2026-02-14T23:40:41+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SQL’de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi\"}]},{\"@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'de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi - 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\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/","og_locale":"tr_TR","og_type":"article","og_title":"SQL'de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi","og_description":"SQL'de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi SQL (Yap\u0131sal Sorgulama Dili), veritabanlar\u0131ndan bilgi almak, eklemek, g\u00fcncellemek ve silmek","og_url":"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2026-02-14T23:40:41+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"5 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"SQL’de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi","datePublished":"2026-02-14T23:40:41+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/"},"wordCount":2915,"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\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/#respond"]}],"copyrightYear":"2026","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/","url":"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/","name":"SQL'de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2026-02-14T23:40:41+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/sqlde-between-ve-in-operatorlerini-kullanma-rehberi\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"SQL’de BETWEEN ve IN Operat\u00f6rlerini Kullanma Rehberi"}]},{"@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\/39128","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=39128"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/39128\/revisions"}],"predecessor-version":[{"id":39129,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/39128\/revisions\/39129"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=39128"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=39128"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=39128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}