{"id":3620,"date":"2024-11-11T17:15:12","date_gmt":"2024-11-11T14:15:12","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/sql-serverda-efcore-8-ile-case-insensitive-anahtar-deger-karsilastirmasi\/"},"modified":"2024-11-11T17:15:12","modified_gmt":"2024-11-11T14:15:12","slug":"sql-serverda-efcore-8-ile-case-insensitive-anahtar-deger-karsilastirmasi","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/sql-serverda-efcore-8-ile-case-insensitive-anahtar-deger-karsilastirmasi\/","title":{"rendered":"SQL Server’da EFCore 8 ile Case-Insensitive Anahtar De\u011fer Kar\u015f\u0131la\u015ft\u0131rmas\u0131"},"content":{"rendered":"

SQL Server’da EFCore 8 ile Case-Insensitive Anahtar De\u011fer Kar\u015f\u0131la\u015ft\u0131rmas\u0131<\/p>\n

Merhaba! Bu makalede, SQL Server’da Entity Framework Core 8 (EFCore 8) ile anahtar de\u011fer kar\u015f\u0131la\u015ft\u0131rmalar\u0131n\u0131n nas\u0131l case-insensitive (b\u00fcy\u00fck k\u00fc\u00e7\u00fck harfe duyarl\u0131 olmayan) \u015fekilde yap\u0131labilece\u011fini inceleyece\u011fiz.<\/p>\n

EFCore 8’de SQL Server’daki veritaban\u0131 tablolar\u0131n\u0131n anahtar de\u011ferlerinin kar\u015f\u0131la\u015ft\u0131r\u0131lmas\u0131 varsay\u0131lan olarak case-sensitive (b\u00fcy\u00fck k\u00fc\u00e7\u00fck harfe duyarl\u0131) \u015fekilde ger\u00e7ekle\u015ftirilir. Bu, \u00f6rne\u011fin “Id” adl\u0131 bir anahtar s\u00fctunu i\u00e7in “id” veya “ID” gibi k\u00fc\u00e7\u00fck veya b\u00fcy\u00fck harf kombinasyonlar\u0131na sahip de\u011ferlerin farkl\u0131 olarak de\u011ferlendirildi\u011fi anlam\u0131na gelir. Bu durum, kodun beklenmedik \u015fekilde davranmas\u0131na veya hata vermesine neden olabilir. Bu sorunu \u00e7\u00f6zmek i\u00e7in birka\u00e7 farkl\u0131 y\u00f6ntem kullanabiliriz.<\/p>\n

Case-Insensitive Kar\u015f\u0131la\u015ft\u0131rmalar i\u00e7in Y\u00f6ntemler<\/h2>\n

EFCore 8’de SQL Server ile case-insensitive anahtar kar\u015f\u0131la\u015ft\u0131rmalar\u0131 sa\u011flamak i\u00e7in birka\u00e7 farkl\u0131 y\u00f6ntem bulunmaktad\u0131r. Bu y\u00f6ntemlerin her biri farkl\u0131 avantajlar ve dezavantajlar sunar. \u0130\u015fte en yayg\u0131n olanlar\u0131:<\/p>\n

1. Veritaban\u0131 Tablosunda Collation Ayarlar\u0131n\u0131 De\u011fi\u015ftirme<\/h3>\n

SQL Server’da veritaban\u0131 tablosunun collation ayarlar\u0131n\u0131 de\u011fi\u015ftirerek case-insensitive kar\u015f\u0131la\u015ft\u0131rmalar sa\u011flayabiliriz. Bu i\u015flem, veritaban\u0131 tablosundaki t\u00fcm s\u00fctunlar i\u00e7in ge\u00e7erlidir. <\/p>\n

\u00d6rnek olarak, “MyTable” adl\u0131 bir tablomuz oldu\u011funu ve “Id” adl\u0131 bir anahtar s\u00fctunu i\u00e7erdi\u011fini varsayal\u0131m. Bu tablonun collation ayar\u0131n\u0131 case-insensitive yapmak i\u00e7in a\u015fa\u011f\u0131daki SQL komutunu kullanabiliriz:<\/p>\n

“`sql
\nALTER TABLE MyTable ALTER COLUMN Id VARCHAR(50) COLLATE SQL_Latin1_General_CP1_CI_AS;
\n“`<\/p>\n

Bu komut, “Id” s\u00fctununun collation ayar\u0131n\u0131 “SQL_Latin1_General_CP1_CI_AS” olarak de\u011fi\u015ftirir. Bu collation, case-insensitive kar\u015f\u0131la\u015ft\u0131rmalar sa\u011flar. Bu y\u00f6ntem, veritaban\u0131 tablosundaki t\u00fcm s\u00fctunlar i\u00e7in ge\u00e7erlidir ve herhangi bir kod de\u011fi\u015fikli\u011fi gerektirmez. Ancak, mevcut verilerinizin collation ayar\u0131na g\u00f6re yeniden olu\u015fturulmas\u0131 gerekebilir.<\/p>\n

2. ConnectionString’de Case-Insensitive Ayar\u0131n\u0131 Belirleme<\/h3>\n

EFCore 8’de connection string’de case-insensitive ayar\u0131 belirterek de case-insensitive kar\u015f\u0131la\u015ft\u0131rmalar sa\u011flayabiliriz. Bu y\u00f6ntem, t\u00fcm ba\u011flant\u0131 i\u00e7in ge\u00e7erlidir ve yaln\u0131zca connection string’e ek bir ayar eklemeyi gerektirir.<\/p>\n

\u00d6rne\u011fin, connection string’e a\u015fa\u011f\u0131daki ayar\u0131n\u0131 ekleyerek case-insensitive kar\u015f\u0131la\u015ft\u0131rmalar sa\u011flayabiliriz:<\/p>\n

“`
\n;MultipleActiveResultSets=True;Application Name=EntityFrameworkCore;
\n“`<\/p>\n

Bu ayar, EFCore’un SQL Server’a case-insensitive ba\u011flant\u0131 olu\u015fturmas\u0131n\u0131 sa\u011flar. Bu y\u00f6ntem, veritaban\u0131 tablolar\u0131ndaki collation ayarlar\u0131n\u0131 de\u011fi\u015ftirmeyi gerektirmez ve kod de\u011fi\u015fikli\u011fi de gerektirmez. Ancak, bu ayar t\u00fcm ba\u011flant\u0131 i\u00e7in ge\u00e7erlidir ve t\u00fcm veritaban\u0131 tablolar\u0131n\u0131 etkiler.<\/p>\n

3. EFCore Konfig\u00fcrasyonlar\u0131nda Case-Insensitive Ayar\u0131n\u0131 Belirleme<\/h3>\n

EFCore’un konfig\u00fcrasyonlar\u0131nda case-insensitive ayar\u0131n\u0131 belirterek de case-insensitive kar\u015f\u0131la\u015ft\u0131rmalar sa\u011flayabiliriz. Bu y\u00f6ntem, belirli bir model veya varl\u0131k t\u00fcr\u00fc i\u00e7in ge\u00e7erlidir ve kod de\u011fi\u015fikli\u011fi gerektirebilir.<\/p>\n

\u00d6rnek olarak, “MyEntity” adl\u0131 bir varl\u0131k t\u00fcr\u00fcm\u00fcz oldu\u011funu varsayal\u0131m. Bu varl\u0131k t\u00fcr\u00fcn\u00fcn anahtar de\u011ferlerinin case-insensitive \u015fekilde kar\u015f\u0131la\u015ft\u0131r\u0131lmas\u0131n\u0131 sa\u011flamak i\u00e7in a\u015fa\u011f\u0131daki kodu kullanabiliriz:<\/p>\n

“`csharp
\nprotected override void OnModelCreating(ModelBuilder modelBuilder)
\n{
\n modelBuilder.Entity().Property(e => e.Id)
\n .HasColumnType(“VARCHAR(50)”)
\n .HasConversion(v => v.ToUpperInvariant(), v => v);
\n}
\n“`<\/p>\n

Bu kod, “Id” s\u00fctunu i\u00e7in case-insensitive kar\u015f\u0131la\u015ft\u0131rmalar\u0131 sa\u011flamak i\u00e7in bir conversion kullan\u0131r. Bu y\u00f6ntem, belirli bir model veya varl\u0131k t\u00fcr\u00fc i\u00e7in ge\u00e7erlidir ve veritaban\u0131 tablolar\u0131n\u0131n collation ayarlar\u0131n\u0131 de\u011fi\u015ftirmeyi gerektirmez. Ancak, kod de\u011fi\u015fikli\u011fi gerektirebilir.<\/p>\n

\u00d6zet<\/h2>\n

SQL Server’da EFCore 8 ile case-insensitive anahtar kar\u015f\u0131la\u015ft\u0131rmalar\u0131 sa\u011flamak i\u00e7in birka\u00e7 farkl\u0131 y\u00f6ntem bulunmaktad\u0131r. Her y\u00f6ntemin farkl\u0131 avantajlar\u0131 ve dezavantajlar\u0131 vard\u0131r. Bu y\u00f6ntemleri do\u011fru \u015fekilde se\u00e7erek kodumuzun beklendi\u011fi gibi davranmas\u0131n\u0131 ve hatalardan ka\u00e7\u0131nmas\u0131n\u0131 sa\u011flayabiliriz.<\/p>\n

Kaynaklar<\/h2>\n