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

[@atibyte]

Thins is very useful, thanks!

[@SD-pf4fw]

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

[@codewithdary]

Thank you so much

[@yuliarahma1300]

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

[@codewithdary]

I definitely will!! :)

[@kmnurunnabi5849]

You are very talented. Keep going on

[@codewithdary]

Thank you so much, I truly appreciate it

[@giorgiofranchini77]

Dary you are the best! Thanks

[@codewithdary]

Thank you too!

[@guyrandalf711]

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

[@codewithdary]

You just need to click on my channel name and you will find them. But here's a link to the playlist: kzbin.info/aero/PLFHz2csJcgk_M6tg-f589Myy-lbLyACKi

[@theJohnCode]

❤

[@codewithdary]

[@HamadAbdulla_7]

Awesome! Thanks

[@codewithdary]

Thank you, Hamad!

[@vugarkhalil]

Respect ❤

[@codewithdary]

Thank you

[@GergelyCsermely]

Thanks

[@codewithdary]

Welcome!!

[@peterf983]

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]

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]

@@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.

[@MohammadAli-s9w7i]

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

[@codewithdary]

What is a convential many-to-many relationship?

[@MohammadAli-s9w7i]

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

[@wmafendi]

big thanks

[@codewithdary]

Thank you for watching :)

[@mounirammi]

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)

[@GreatCaleb]

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

[@codewithdary]

You are completely right....

[@GreatCaleb]

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

[@nazar87ali]

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

[@codewithdary]

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

[@nazar87ali]

and how can add more Customize in app

[@codewithdary]

Please define "more"

[@foantje5857]

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

[@codewithdary]

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

[@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]

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

[@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]

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

[@sandeepbhambre]

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]

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 :)

[@tintrung3785]

"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]

php artisan migrate:fresh