{"id":30519,"date":"2025-09-28T21:41:04","date_gmt":"2025-09-28T18:41:04","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=30519"},"modified":"2025-09-28T21:41:04","modified_gmt":"2025-09-28T18:41:04","slug":"symfony2-ile-vps-uzerinde-crud-islemleri-gerceklestirme-derinlemesine-inceleme-bolum-2","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/symfony2-ile-vps-uzerinde-crud-islemleri-gerceklestirme-derinlemesine-inceleme-bolum-2\/","title":{"rendered":"Symfony2 ile VPS \u00dczerinde CRUD \u0130\u015flemleri Ger\u00e7ekle\u015ftirme: Derinlemesine \u0130nceleme (B\u00f6l\u00fcm 2)"},"content":{"rendered":"

<\/p>\n

Symfony2 ile VPS \u00dczerinde CRUD \u0130\u015flemleri Ger\u00e7ekle\u015ftirme: Derinlemesine \u0130nceleme (B\u00f6l\u00fcm 2)<\/h2>\n

Bu makale serisinin ilk b\u00f6l\u00fcm\u00fcnde, Symfony2 projesi olu\u015fturma, veritaban\u0131 ba\u011flant\u0131s\u0131n\u0131 yap\u0131land\u0131rma ve Doctrine ORM kullanarak basit bir Entity tan\u0131mlama gibi temel konulara de\u011finmi\u015ftik. Bir Sanal \u00d6zel Sunucu (VPS) \u00fczerinde Symfony2 uygulamas\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rman\u0131n ilk ad\u0131mlar\u0131n\u0131 atm\u0131\u015f, web sunucusu yap\u0131land\u0131rmas\u0131na (genellikle Nginx veya Apache) genel bir bak\u0131\u015f sunmu\u015ftuk. \u015eimdi, bu sa\u011flam temel \u00fczerine in\u015fa ederek, Symfony2’nin CRUD (Create, Read, Update, Delete) operasyonlar\u0131 i\u00e7in sundu\u011fu g\u00fc\u00e7l\u00fc ve esnek ara\u00e7lar\u0131 daha derinlemesine inceleyece\u011fiz. \u00d6zellikle, form y\u00f6netimi, veri do\u011frulama, kullan\u0131c\u0131 geri bildirimleri ve g\u00fcvenlik gibi \u00f6nemli konulara odaklanarak, bir web uygulamas\u0131n\u0131n belkemi\u011fini olu\u015fturan bu i\u015flemleri nas\u0131l etkin bir \u015fekilde ger\u00e7ekle\u015ftirebilece\u011finizi ad\u0131m ad\u0131m g\u00f6sterece\u011fiz.<\/p>\n

CRUD Operasyonlar\u0131na Derinlemesine Bak\u0131\u015f<\/h3>\n

CRUD operasyonlar\u0131, hemen hemen her veri odakl\u0131 uygulaman\u0131n temelini olu\u015fturur. Symfony2, bu i\u015flemleri kolayla\u015ft\u0131rmak i\u00e7in Doctrine ORM, Form Bile\u015feni ve Validasyon Bile\u015feni gibi g\u00fc\u00e7l\u00fc ara\u00e7lar sunar. Bu b\u00f6l\u00fcmde, her bir CRUD operasyonunu ayr\u0131 ayr\u0131 ele alacak ve en iyi uygulamalar\u0131 sergileyece\u011fiz.<\/p>\n

Yeni Kay\u0131t Olu\u015fturma (Create)<\/h4>\n

Yeni bir veri kayd\u0131 olu\u015fturmak, genellikle bir HTML formu arac\u0131l\u0131\u011f\u0131yla kullan\u0131c\u0131dan bilgi almay\u0131 ve bu bilgileri veritaban\u0131na kaydetmeyi i\u00e7erir. Symfony’de bu s\u00fcre\u00e7, Form Bile\u015feni sayesinde olduk\u00e7a basittir ve bir\u00e7ok g\u00fcvenlik ve do\u011frulama \u00f6zelli\u011fini beraberinde getirir.<\/p>\n

Form Olu\u015fturma ve Yap\u0131land\u0131rma<\/h5>\n

\u00d6ncelikle, Part 1’de olu\u015fturdu\u011fumuz Product<\/code> entity’si i\u00e7in bir form tipi olu\u015fturmal\u0131y\u0131z. Bu, src\/AppBundle\/Form\/ProductType.php<\/code> gibi bir dosyada yap\u0131labilir:<\/p>\n

\/\/ src\/AppBundle\/Form\/ProductType.php\nnamespace AppBundle\\Form;\n\nuse AppBundle\\Entity\\Product;\nuse Symfony\\Component\\Form\\AbstractType;\nuse Symfony\\Component\\Form\\FormBuilderInterface;\nuse Symfony\\Component\\OptionsResolver\\OptionsResolverInterface;\nuse Symfony\\Component\\Form\\Extension\\Core\\Type\\TextType;\nuse Symfony\\Component\\Form\\Extension\\Core\\Type\\NumberType;\nuse Symfony\\Component\\Form\\Extension\\Core\\Type\\TextareaType;\nuse Symfony\\Component\\Form\\Extension\\Core\\Type\\SubmitType;\n\nclass ProductType extends AbstractType\n{\n    public function buildForm(FormBuilderInterface $builder, array $options)\n    {\n        $builder\n            ->add('name', TextType::class, ['label' => '\u00dcr\u00fcn Ad\u0131'])\n            ->add('price', NumberType::class, ['label' => 'Fiyat'])\n            ->add('description', TextareaType::class, ['label' => 'A\u00e7\u0131klama', 'required' => false])\n            ->add('save', SubmitType::class, ['label' => 'Kaydet']);\n    }\n\n    public function setDefaultOptions(OptionsResolverInterface $resolver)\n    {\n        $resolver->setDefaults([\n            'data_class' => Product::class,\n        ]);\n    }\n\n    public function getName()\n    {\n        return 'product';\n    }\n}<\/code><\/pre>\n
Bu form tipi, Product<\/code> entity’mizin alanlar\u0131na kar\u015f\u0131l\u0131k gelen form alanlar\u0131n\u0131 tan\u0131mlar. data_class<\/code> se\u00e7ene\u011fi, formun hangi entity ile ili\u015fkilendirilece\u011fini Symfony’ye bildirir.<\/p>\n
Controller Taraf\u0131nda Form \u0130\u015fleme<\/h5>\n
\u015eimdi, bu formu bir Controller i\u00e7inde nas\u0131l kullanaca\u011f\u0131m\u0131za bakal\u0131m. Yeni bir \u00fcr\u00fcn eklemek i\u00e7in bir eylem (Action<\/code>) tan\u0131mlayal\u0131m:<\/p>\n
\/\/ src\/AppBundle\/Controller\/ProductController.php\nnamespace AppBundle\\Controller;\n\nuse AppBundle\\Entity\\Product;\nuse AppBundle\\Form\\ProductType;\nuse Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller;\nuse Symfony\\Component\\HttpFoundation\\Request;\nuse Symfony\\Component\\Routing\\Annotation\\Route;\n\nclass ProductController extends Controller\n{\n    \/<\/em>\n     * @Route(\"\/product\/new\", name=\"product_new\")\n     *\/\n    public function newAction(Request $request)\n    {\n        $product = new Product();\n        $form = $this->createForm(ProductType::class, $product);\n\n        $form->handleRequest($request);\n\n        if ($form->isSubmitted() && $form->isValid()) {\n            $em = $this->getDoctrine()->getManager();\n            $em->persist($product); \/\/ Entity'yi kal\u0131c\u0131 hale getir\n            $em->flush(); \/\/ Veritaban\u0131na kaydet\n\n            $this->addFlash(\n                'notice',\n                '\u00dcr\u00fcn ba\u015far\u0131yla eklendi!'\n            );\n\n            return $this->redirectToRoute('product_list'); \/\/ Ba\u015far\u0131l\u0131ysa \u00fcr\u00fcn listesine y\u00f6nlendir\n        }\n\n        return $this->render('product\/new.html.twig', [\n            'form' => $form->createView(),\n        ]);\n    }\n}<\/code><\/pre>\n
Bu kodda:
\n*   Yeni bir Product<\/code> nesnesi olu\u015fturulur.
\n*   ProductType<\/code> kullan\u0131larak bir form olu\u015fturulur ve Product<\/code> nesnesi ile ili\u015fkilendirilir.
\n*   handleRequest($request)<\/code> metodu, gelen HTTP iste\u011findeki verileri forma ba\u011flar.
\n*   isSubmitted()<\/code> ve isValid()<\/code> metotlar\u0131, formun g\u00f6nderilip g\u00f6nderilmedi\u011fini ve verilerin ge\u00e7erli olup olmad\u0131\u011f\u0131n\u0131 kontrol eder.
\n*   Veriler ge\u00e7erliyse, persist()<\/code> ile entity Doctrine taraf\u0131ndan izlenmeye ba\u015flan\u0131r ve flush()<\/code> ile veritaban\u0131na kaydedilir.
\n*   addFlash()<\/code> metodu, kullan\u0131c\u0131ya geri bildirim sa\u011flamak i\u00e7in bir “flash mesaj\u0131” ekler. Bu mesajlar, bir sonraki HTTP iste\u011fi i\u00e7in saklan\u0131r ve genellikle Twig \u015fablonunda g\u00f6r\u00fcnt\u00fclenir.
\n*   \u0130\u015flem ba\u015far\u0131l\u0131 olursa, kullan\u0131c\u0131 \u00fcr\u00fcn listesi sayfas\u0131na y\u00f6nlendirilir.<\/p>\n
Twig \u015eablonunda Formu G\u00f6r\u00fcnt\u00fcleme<\/h5>\n
Son olarak, formu g\u00f6r\u00fcnt\u00fclemek i\u00e7in app\/Resources\/views\/product\/new.html.twig<\/code> dosyas\u0131n\u0131 olu\u015ftural\u0131m:<\/p>\n
{# app\/Resources\/views\/product\/new.html.twig #}\n{% extends 'base.html.twig' %}\n\n{% block body %}\n    
Yeni \u00dcr\u00fcn Ekle<\/h2>\n\n    {% for message in app.flashes('notice') %}\n        
\n            {{ message }}\n        <\/div>\n    {% endfor %}\n\n    {{ form_start(form) }}\n        {{ form_row(form.name) }}\n        {{ form_row(form.price) }}\n        {{ form_row(form.description) }}\n        {{ form_row(form.save) }}\n    {{ form_end(form) }}\n{% endblock %}<\/code><\/pre>\n
Bu \u015fablonda form_start()<\/code>, form_row()<\/code> ve form_end()<\/code> gibi Twig fonksiyonlar\u0131, formun HTML \u00e7\u0131kt\u0131s\u0131n\u0131 kolayca olu\u015fturmak i\u00e7in kullan\u0131l\u0131r. app.flashes('notice')<\/code> ile daha \u00f6nce ekledi\u011fimiz flash mesajlar\u0131 g\u00f6r\u00fcnt\u00fclenir.<\/p>\n
Kay\u0131tlar\u0131 Listeleme (Read – All)<\/h4>\n
Veritaban\u0131ndaki t\u00fcm \u00fcr\u00fcnleri listelemek, genellikle bir Controller’dan Repository arac\u0131l\u0131\u011f\u0131yla veri \u00e7ekmeyi ve bu verileri bir Twig \u015fablonunda g\u00f6r\u00fcnt\u00fclemeyi i\u00e7erir.<\/p>\n
Controller Taraf\u0131nda Veri \u00c7ekme<\/h5>\n
\/\/ src\/AppBundle\/Controller\/ProductController.php\n\/\/ ...\nclass ProductController extends Controller\n{\n    \/<\/em>\n     * @Route(\"\/product\", name=\"product_list\")\n     *\/\n    public function listAction()\n    {\n        $products = $this->getDoctrine()\n            ->getRepository(Product::class)\n            ->findAll(); \/\/ T\u00fcm \u00fcr\u00fcnleri getir\n\n        return $this->render('product\/list.html.twig', [\n            'products' => $products,\n        ]);\n    }\n}<\/code><\/pre>\n
Burada, getRepository(Product::class)<\/code> ile Product<\/code> entity’mizin Repository’sine eri\u015firiz. findAll()<\/code> metodu, veritaban\u0131ndaki t\u00fcm Product<\/code> kay\u0131tlar\u0131n\u0131 d\u00f6nd\u00fcr\u00fcr.<\/p>\n
Twig \u015eablonunda Listeyi G\u00f6r\u00fcnt\u00fcleme<\/h5>\n
app\/Resources\/views\/product\/list.html.twig<\/code> dosyas\u0131n\u0131 olu\u015ftural\u0131m:<\/p>\n
{# app\/Resources\/views\/product\/list.html.twig #}\n{% extends 'base.html.twig' %}\n\n{% block body %}\n    
\u00dcr\u00fcn Listesi<\/h2>\n\n    
Yeni \u00dcr\u00fcn Ekle<\/a><\/p>\n\n    {% for message in app.flashes('notice') %}\n        
\n            {{ message }}\n        <\/div>\n    {% endfor %}\n\n    {% if products is not empty %}\n        \n            \n                \n                    \n                {% for product in products %}\n                    \n                        
ID<\/th>\n                    Ad\u0131<\/th>\n                    Fiyat<\/th>\n                    A\u00e7\u0131klama<\/th>\n                    \u0130\u015flemler<\/th>\n                <\/tr>\n            <\/thead>\n            
{{ product.id }}<\/td>\n                        {{ product.name }}<\/td>\n                        {{ product.price|number_format(2, ',', '.') }} TL<\/td>\n                        {{ product.description|length > 50 ? product.description|slice(0, 50) ~ '...' : product.description }}<\/td>\n                        \n                            G\u00f6r\u00fcnt\u00fcle<\/a>\n                            D\u00fczenle<\/a>\n                            Sil<\/a>\n                        <\/td>\n                    <\/tr>\n                {% endfor %}\n            <\/tbody>\n        <\/table>\n    {% else %}\n        
Hen\u00fcz hi\u00e7 \u00fcr\u00fcn eklenmemi\u015f.<\/p>\n    {% endif %}\n{% endblock %}<\/code><\/pre>\n
Bu \u015fablon, \u00fcr\u00fcnleri bir tablo i\u00e7inde listeler ve her \u00fcr\u00fcn i\u00e7in g\u00f6r\u00fcnt\u00fcleme, d\u00fczenleme ve silme ba\u011flant\u0131lar\u0131 sunar.<\/p>\n
Tek Kay\u0131t G\u00f6r\u00fcnt\u00fcleme (Read – One)<\/h4>\n
Belirli bir \u00fcr\u00fcn\u00fcn detaylar\u0131n\u0131 g\u00f6r\u00fcnt\u00fclemek i\u00e7in, genellikle URL’den bir ID parametresi al\u0131n\u0131r ve bu ID’ye g\u00f6re veritaban\u0131ndan tek bir kay\u0131t \u00e7ekilir.<\/p>\n
Controller Taraf\u0131nda Tek Kay\u0131t \u00c7ekme<\/h5>\n
\/\/ src\/AppBundle\/Controller\/ProductController.php\n\/\/ ...\nclass ProductController extends Controller\n{\n    \/<\/em>\n     * @Route(\"\/product\/{id}\", name=\"product_show\")\n     *\/\n    public function showAction($id)\n    {\n        $product = $this->getDoctrine()\n            ->getRepository(Product::class)\n            ->find($id); \/\/ ID'ye g\u00f6re \u00fcr\u00fcn\u00fc bul\n\n        if (!$product) {\n            throw $this->createNotFoundException('\u00dcr\u00fcn bulunamad\u0131: ' . $id);\n        }\n\n        return $this->render('product\/show.html.twig', [\n            'product' => $product,\n        ]);\n    }\n}<\/code><\/pre>\n
find($id)<\/code> metodu, belirtilen ID’ye sahip entity’yi d\u00f6nd\u00fcr\u00fcr. E\u011fer \u00fcr\u00fcn bulunamazsa, createNotFoundException()<\/code> ile bir 404 hatas\u0131 f\u0131rlat\u0131l\u0131r.<\/p>\n
Twig \u015eablonunda Detaylar\u0131 G\u00f6r\u00fcnt\u00fcleme<\/h5>\n
app\/Resources\/views\/product\/show.html.twig<\/code> dosyas\u0131n\u0131 olu\u015ftural\u0131m:<\/p>\n
{# app\/Resources\/views\/product\/show.html.twig #}\n{% extends 'base.html.twig' %}\n\n{% block body %}\n    
\u00dcr\u00fcn Detay\u0131: {{ product.name }}<\/h2>\n\n    \n        \n            \n                \n                \n                \n                
ID<\/th>\n                {{ product.id }}<\/td>\n            <\/tr>\n            
Ad\u0131<\/th>\n                {{ product.name }}<\/td>\n            <\/tr>\n            
Fiyat<\/th>\n                {{ product.price|number_format(2, ',', '.') }} TL<\/td>\n            <\/tr>\n            
A\u00e7\u0131klama<\/th>\n                {{ product.description|default('A\u00e7\u0131klama yok.')|nl2br }}<\/td>\n            <\/tr>\n        <\/tbody>\n    <\/table>\n\n    
\n        Listeye Geri D\u00f6n<\/a>\n        D\u00fczenle<\/a>\n    <\/p>\n{% endblock %}<\/code><\/pre>\n
Kay\u0131t G\u00fcncelleme (Update)<\/h4>\n
Mevcut bir kayd\u0131 g\u00fcncellemek, yeni kay\u0131t olu\u015fturmaya benzer, ancak formun mevcut veri ile doldurulmas\u0131 ve veritaban\u0131nda sadece flush()<\/code> \u00e7a\u011fr\u0131lmas\u0131 yeterlidir.<\/p>\n
Controller Taraf\u0131nda Kay\u0131t G\u00fcncelleme<\/h5>\n
\/\/ src\/AppBundle\/Controller\/ProductController.php\n\/\/ ...\nclass ProductController extends Controller\n{\n    \/<\/em>\n     * @Route(\"\/product\/{id}\/edit\", name=\"product_edit\")\n     *\/\n    public function editAction(Request $request, $id)\n    {\n        $em = $this->getDoctrine()->getManager();\n        $product = $em->getRepository(Product::class)->find($id);\n\n        if (!$product) {\n            throw $this->createNotFoundException('G\u00fcncellenecek \u00fcr\u00fcn bulunamad\u0131: ' . $id);\n        }\n\n        $form = $this->createForm(ProductType::class, $product);\n        $form->handleRequest($request);\n\n        if ($form->isSubmitted() && $form->isValid()) {\n            $em->flush(); \/\/ Sadece flush yeterli, persist zaten yap\u0131ld\u0131\n\n            $this->addFlash(\n                'notice',\n                '\u00dcr\u00fcn ba\u015far\u0131yla g\u00fcncellendi!'\n            );\n\n            return $this->redirectToRoute('product_show', ['id' => $product->getId()]);\n        }\n\n        return $this->render('product\/edit.html.twig', [\n            'form' => $form->createView(),\n            'product' => $product,\n        ]);\n    }\n}<\/code><\/pre>\n
Burada dikkat edilmesi gereken nokta, form olu\u015fturulurken mevcut $product<\/code> nesnesinin ikinci parametre olarak ge\u00e7irilmesidir. Bu, formun mevcut verilerle doldurulmas\u0131n\u0131 sa\u011flar. flush()<\/code> \u00e7a\u011fr\u0131ld\u0131\u011f\u0131nda, Doctrine, izledi\u011fi $product<\/code> nesnesindeki de\u011fi\u015fiklikleri otomatik olarak veritaban\u0131na yans\u0131t\u0131r.<\/p>\n
Twig \u015eablonunda G\u00fcncelleme Formu<\/h5>\n
app\/Resources\/views\/product\/edit.html.twig<\/code> dosyas\u0131n\u0131 olu\u015ftural\u0131m:<\/p>\n
{# app\/Resources\/views\/product\/edit.html.twig #}\n{% extends 'base.html.twig' %}\n\n{% block body %}\n    
\u00dcr\u00fcn D\u00fczenle: {{ product.name }}<\/h2>\n\n    {% for message in app.flashes('notice') %}\n        
\n            {{ message }}\n        <\/div>\n    {% endfor %}\n\n    {{ form_start(form) }}\n        {{ form_row(form.name) }}\n        {{ form_row(form.price) }}\n        {{ form_row(form.description) }}\n        {{ form_row(form.save, {'label': 'G\u00fcncelle'}) }}\n    {{ form_end(form) }}\n\n    
\u0130ptal<\/a><\/p>\n{% endblock %}<\/code><\/pre>\n
Kay\u0131t Silme (Delete)<\/h4>\n
Bir kayd\u0131 silmek, di\u011fer operasyonlara g\u00f6re daha basit g\u00f6r\u00fcnse de, g\u00fcvenlik ve kullan\u0131c\u0131 onay\u0131 a\u00e7\u0131s\u0131ndan dikkatli olunmas\u0131 gereken bir i\u015flemdir.<\/p>\n
Controller Taraf\u0131nda Kay\u0131t Silme<\/h5>\n
\/\/ src\/AppBundle\/Controller\/ProductController.php\n\/\/ ...\nclass ProductController extends Controller\n{\n    \/<\/em>\n     * @Route(\"\/product\/{id}\/delete\", name=\"product_delete\", methods={\"POST\"})\n     *\/\n    public function deleteAction(Request $request, $id)\n    {\n        $em = $this->getDoctrine()->getManager();\n        $product = $em->getRepository(Product::class)->find($id);\n\n        if (!$product) {\n            throw $this->createNotFoundException('Silinecek \u00fcr\u00fcn bulunamad\u0131: ' . $id);\n        }\n\n        \/\/ G\u00fcvenlik i\u00e7in CSRF token kontrol\u00fc \u00f6nerilir.\n        \/\/ Symfony 2'de bunu manuel yapman\u0131z gerekebilir veya bir form kullanarak.\n        \/\/ Basit bir \u00f6rnek i\u00e7in \u015fimdilik atl\u0131yoruz, ancak \u00fcretimde kullanmay\u0131n.\n        \/\/ Daha g\u00fcvenli bir yakla\u015f\u0131m i\u00e7in a\u015fa\u011f\u0131daki \"G\u00fcvenlik\" b\u00f6l\u00fcm\u00fcne bak\u0131n.\n\n        $em->remove($product); \/\/ Entity'yi silme i\u00e7in i\u015faretle\n        $em->flush(); \/\/ Veritaban\u0131ndan sil\n\n        $this->addFlash(\n            'notice',\n            '\u00dcr\u00fcn ba\u015far\u0131yla silindi!'\n        );\n\n        return $this->redirectToRoute('product_list');\n    }\n}<\/code><\/pre>\n
remove($product)<\/code> metodu, entity’yi silinmek \u00fczere i\u015faretler. flush()<\/code> \u00e7a\u011fr\u0131ld\u0131\u011f\u0131nda, Doctrine bu entity’yi veritaban\u0131ndan siler. methods={\"POST\"}<\/code> ile bu rotan\u0131n sadece POST istekleriyle eri\u015filebilir oldu\u011funu belirtmek, yanl\u0131\u015fl\u0131kla silme i\u015flemlerini \u00f6nlemeye yard\u0131mc\u0131 olur. Ancak bu yeterli de\u011fildir, CSRF korumas\u0131 kesinlikle gereklidir.<\/p>\n
G\u00fcvenli Silme \u0130\u015flemleri (CSRF Korumas\u0131)<\/h5>\n
Bir GET<\/code> iste\u011fi ile silme i\u015flemi yapmak, CSRF (Cross-Site Request Forgery) sald\u0131r\u0131lar\u0131na a\u00e7\u0131k kap\u0131 b\u0131rak\u0131r. Bu nedenle, silme i\u015flemleri i\u00e7in her zaman POST<\/code> istekleri ve CSRF token’\u0131 kullan\u0131lmal\u0131d\u0131r. Bunun i\u00e7in, silme linki yerine k\u00fc\u00e7\u00fck bir form kullanmak en iyi yoldur:<\/p>\n
{# product\/list.html.twig veya product\/show.html.twig i\u00e7inde #}\n
\n     {# Symfony'nin MethodOverrideListener'\u0131 i\u00e7in #}\n     {# CSRF token #}\n