Defining Our Migrations, Models & Relationships for FilamentPHP - FilamentPHP for Beginners

Поділитися
Вставка
  • Опубліковано 14 січ 2025

КОМЕНТАРІ • 47

  • @SD-pf4fw
    @SD-pf4fw Рік тому +1

    This is so well organised and detailed, great tutorial keep it going will watch the whole filament series

  • @giorgiofranchini77
    @giorgiofranchini77 Рік тому +1

    Dary you are the best! Thanks

  • @kmnurunnabi5849
    @kmnurunnabi5849 Рік тому +2

    You are very talented. Keep going on

    • @codewithdary
      @codewithdary  Рік тому +1

      Thank you so much, I truly appreciate it

  • @yuliarahma1300
    @yuliarahma1300 Рік тому +2

    very nice, keep going please, more about filament v3, love it.

  • @atibyte
    @atibyte 2 місяці тому

    Thins is very useful, thanks!

  • @guyrandalf711
    @guyrandalf711 Рік тому

    Great! Please can you add links to the previous tutorials?

    • @codewithdary
      @codewithdary  Рік тому +1

      You just need to click on my channel name and you will find them. But here's a link to the playlist: ua-cam.com/play/PLFHz2csJcgk_M6tg-f589Myy-lbLyACKi.html

  • @vugarkhalil
    @vugarkhalil Рік тому +1

    Respect ❤

  • @HamadAbdulla_7
    @HamadAbdulla_7 Рік тому

    Awesome! Thanks

  • @wmafendi
    @wmafendi Рік тому +1

    big thanks

  • @GergelyCsermely
    @GergelyCsermely Рік тому +1

    Thanks

  • @theJohnCode
    @theJohnCode Рік тому +1

  • @MohammadAli-s9w7i
    @MohammadAli-s9w7i Рік тому +1

    Hi there,
    Quick question
    Why not to use conventional many-to-many relationship between Order and Product?

    • @codewithdary
      @codewithdary  Рік тому

      What is a convential many-to-many relationship?

    • @MohammadAli-s9w7i
      @MohammadAli-s9w7i Рік тому

      @@codewithdary
      Using belongsToMany() on both models and making a pivot table/model I assume.

  • @foantje5857
    @foantje5857 Рік тому +1

    why u make the pivot tables and models isn't that being made automatically?

    • @codewithdary
      @codewithdary  Рік тому

      Not from my understanding, I've never seen it being generated automatically. Can you explain how?

    • @foantje5857
      @foantje5857 Рік тому

      @@codewithdary well when u define the foreign key and migrate fresh u automatically get the pivot table. I don’t make pivot models don’t see the point

    • @codewithdary
      @codewithdary  Рік тому

      @@foantje5857 how does Laravel knows what relationship it is when you don’t define it in your migration? 😅

    • @foantje5857
      @foantje5857 Рік тому

      @@codewithdary thats not what i said u define it in the migration i just don’t make a pivot model and i don’t make a seperate pivot migration

    • @codewithdary
      @codewithdary  Рік тому

      @@foantje5857 you said why u make the pivot tables my friend :)

  • @peterf983
    @peterf983 Рік тому +1

    Someone might says that storing Product's price in table column as numeric is bad idea. Isn't it better to store Product's price as integer and convert it to decimal in view/controller code?

    • @codewithdary
      @codewithdary  Рік тому

      Honestly, I have never heard that before. Storing a product's price as an integer and converting it to decimal in the view/controller code can work, but it is generally not a good idea. This approach can make it more difficult to perform calculations and comparisons on the price data within the database itself. It is generally recommended to store prices as a decimal data type in the database to ensure accuracy and consistency.

    • @pasizdobrekuce
      @pasizdobrekuce Рік тому +2

      @@codewithdary we store it in cents at my work, and convert it to human friendly values for frontend. Not a good idea indeed. Hard to maintain and reason about.

  • @mounirammi
    @mounirammi 7 місяців тому

    Hi. Whe i'm getting this error when trying to access the orders page !
    SQLSTATE[42S22]: Column not found: 1054 Unknown column 'orders.deleted_at' in 'where clause' (Connection: mysql, SQL: select count(*) as aggregate from `orders` where `orders`.`deleted_at` is null)

  • @nazar87ali
    @nazar87ali Рік тому +1

    and how can add more Customize in app

  • @sandeepbhambre
    @sandeepbhambre Рік тому +1

    In this video you deleted $table->timestamps(); from the "create_category_product_table" migration. But, while defining the relationship, you added withTimestamps(). How is it possible?

    • @codewithdary
      @codewithdary  Рік тому

      The withTimestamps() method on a many-to-many relationship in Laravel automatically updates the created_at and updated_at timestamps on the pivot table that joins the two related models. The timestamps on the pivot table will be managed by the withTimestamps() method on the relationship definition :)

  • @GreatCaleb
    @GreatCaleb Рік тому +2

    I think the relationship in the Brand model should be name products instead of brands

    • @codewithdary
      @codewithdary  Рік тому +1

      You are completely right....

    • @GreatCaleb
      @GreatCaleb Рік тому +1

      @@codewithdary thank you for all your contents they are very helpful to us junior programmer

  • @tintrung3785
    @tintrung3785 10 місяців тому

    "SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'categories' already exists (Connection: mysql, SQL: create table `categories` (`id` bigint unsigned not null auto_increment primary key, `name` varchar(255) not null, `slug` varchar(255) not null, `is_visible` tinyint(1) not null default '0', `description` longtext null, `created_at` timestamp null, `updated_at` timestamp null) default character set utf8mb4 collate 'utf8mb4_unicode_ci')" Please help me fix this when I use the PHP artisan migrate command !

    • @kenjivafe
      @kenjivafe 10 місяців тому

      php artisan migrate:fresh

  • @nazar87ali
    @nazar87ali Рік тому +1

    pleas in next video explain how can add another language to app

    • @codewithdary
      @codewithdary  Рік тому +1

      That won't be added in the first FilamentPHP series on my channel. But definitely a topic I will cover in the future :)