great training thanks! I was confused by the Emily Williams example. At 1:19:13 she was client_id: "689944a1-6655-45b2-944a-e0ef73905feb" and then after 1:24:57 she was client_id: "afe8c2a3-3d38-4c0b-afca-23ce643d50f9" Both had the same address, zip, city, name. Why the change??
Merci Guillaume! J'aurais espéré avoir le cours en français mais ca va faire le travail! Je vais suivre ta chaine et merci pour tous le contenus. Bonjour de Montréal, Québec.
Just a point to note :) There is no need of surrounding the async Supabase operation code with a try catch block since if an error occurs during the execution of the asynchronous operation, it will be captured in the error variable that you destructor and you can check for errors there.
Sorry I'm a newbie so may be a silly question, but what if there is an issue with calling supabase itself, not the error from db, but may be some network issue or some unexpected exception? Do we still need the try/catch? Thank you in advance
@@Munk-tt6tz If supabase gives you an error, then no need for try catch. Like for the CRUD operations, you destructure { error }, so any types of exception whether network went off etc. that may arise from doing the operation will be captured by without try catch.
What this video is: a showcase of Supabase's capabilities and when to use them. What this video is NOT: a tutorial showing how to build a working application with Supabase. When you finish, you should understand the advantages of using Supabase, but you won't have actually implemented a working application. Personally, that was what I was looking for.
The lack of a demo makes this video very lacking. I don't understand people who make these videos. Its like telling you how to make a chicken soup but never shows the final result.
Hi Guillaume, nice work ! There is something off about the recover password section. You are recovering the password while you are still authenticated. I believe that we recover the password because we can't authenticate. Also, the link does not contain any unique parameters, what prevents us from just navigating to the recovery URL ?
1. Supabase recovers/updates password only when you are authenticated, this can be seen when you click the recovery email sent, it automatically sends a token and logs you in even though you were not previously logged in. That is just how it works you have to be logged in to update password whether you logged in via the login form or from clicking the password reset link which auto logs you in. 2. The link contains some unique parameters with the access token, it changes so fast you can barely see it but you can write code to capture the access token and check if it is there and maybe find a means to verify if it is a legit one sent from Supabase not just user typed. Moreover, you can prevent one from accessing the recovery URL by checking if the user is logged in, if not redirect back to another URL of your choice with an error toaster. You can get the code of getting the current user if logged in from the Supabase docs.
Supabase cannot be an alternative to Firebase in the truest sense since Supabase is a good Relational Database Solution, whereas Firebase is a good NoSQL database with other capabilities.
@@juliobonella8711 Never thought I'll be commenting back over here 😂 It was a year ago and at the time Supabase was good at being a SQL database. On the other side Firebase was already providing realtime database, firestore, storage, cloud messaging, authentication service. Things have changed since then, obviously.
Thank you for the tutorial. Does it also for Javascript students that aren't familiar with Typescript, As well as React students who aren't familiar with Vue?
I have an application made with react js and Supabase I would like to know how I can make it so that the administrator profile can create, edit, update, delete seller type profile users, that is, so that seller type users can enter or authenticate in the application they have to be previously created by the administrator from their profile, the administrator provides the seller-type users with a name and password by another means, whether paper or other means, and the users enter the data provided by the administrator and if they are correct, they enter to your seller profile, how can I implement this functionality using only react js and Supabase, without needing to use Node js and express
Instead of creating a tutorial for people who can't read what's in front of them, how about creating one where the supposed teacher explains why they're doing what they're doing... you know, how a tutorial is supposed to be?
Hello everyone! I hope you will enjoy this course on Supabase as much as I enjoyed creating it :) Best !
You are the best Guillaume!
It was awesome 🎉 ❤
great training thanks!
I was confused by the Emily Williams example. At
1:19:13 she was client_id: "689944a1-6655-45b2-944a-e0ef73905feb" and then after
1:24:57 she was client_id: "afe8c2a3-3d38-4c0b-afca-23ce643d50f9"
Both had the same address, zip, city, name.
Why the change??
Thank you sir!
Merci Guillaume! J'aurais espéré avoir le cours en français mais ca va faire le travail! Je vais suivre ta chaine et merci pour tous le contenus. Bonjour de Montréal, Québec.
Great tutorial. Please consider having the URL address bar in the video shots It helps those of us who are paying attention to routing.
I have been hosting postgres dbs on supabase for a long time and tbh it is quite reliable
Just a point to note :) There is no need of surrounding the async Supabase operation code with a try catch block since if an error occurs during the execution of the asynchronous operation, it will be captured in the error variable that you destructor and you can check for errors there.
Sorry I'm a newbie so may be a silly question, but what if there is an issue with calling supabase itself, not the error from db, but may be some network issue or some unexpected exception? Do we still need the try/catch? Thank you in advance
@@Munk-tt6tz If supabase gives you an error, then no need for try catch. Like for the CRUD operations, you destructure { error }, so any types of exception whether network went off etc. that may arise from doing the operation will be captured by without try catch.
What this video is: a showcase of Supabase's capabilities and when to use them. What this video is NOT: a tutorial showing how to build a working application with Supabase.
When you finish, you should understand the advantages of using Supabase, but you won't have actually implemented a working application. Personally, that was what I was looking for.
Agreed!
It wasn't a "Full Tutorial" but a very very long ad.
Thank you for this video!! It's exactly what I have been needing and looking for
I came here to learn Supabase. Then I found that I need to learn Postgres first 😅
The lack of a demo makes this video very lacking. I don't understand people who make these videos. Its like telling you how to make a chicken soup but never shows the final result.
Thanks for this video. It was a very helpful crash course and gave me everything that I needed to know 👏
Great a french tutorial !
Awesome accent, awesome tutorial! 😜
Thanks for sharing with the community, keep it up! 👍
Hi Guillaume, nice work ! There is something off about the recover password section. You are recovering the password while you are still authenticated. I believe that we recover the password because we can't authenticate. Also, the link does not contain any unique parameters, what prevents us from just navigating to the recovery URL ?
1. Supabase recovers/updates password only when you are authenticated, this can be seen when you click the recovery email sent, it automatically sends a token and logs you in even though you were not previously logged in. That is just how it works you have to be logged in to update password whether you logged in via the login form or from clicking the password reset link which auto logs you in.
2. The link contains some unique parameters with the access token, it changes so fast you can barely see it but you can write code to capture the access token and check if it is there and maybe find a means to verify if it is a legit one sent from Supabase not just user typed. Moreover, you can prevent one from accessing the recovery URL by checking if the user is logged in, if not redirect back to another URL of your choice with an error toaster. You can get the code of getting the current user if logged in from the Supabase docs.
absolutely i noticed that too
Fantastic video. Now Supabase works slightly different, are you considering update this? thanks a lot and, once again, great content
Damn - I thought it was Wil Wheaton for a few seconds there. 😆
Thanks for this amazing course.
i like this bro style
Supabase cannot be an alternative to Firebase in the truest sense since Supabase is a good Relational Database Solution, whereas Firebase is a good NoSQL database with other capabilities.
How do you implement Full Text Search in Firebase?
@@bilalbilalbilal7 nah they don't have than on firebase + queries are limited too
Why not? They are backend alternatives.
@@juliobonella8711 Never thought I'll be commenting back over here 😂 It was a year ago and at the time Supabase was good at being a SQL database. On the other side Firebase was already providing realtime database, firestore, storage, cloud messaging, authentication service. Things have changed since then, obviously.
Thank you for the tutorial.
Does it also for Javascript students that aren't familiar with Typescript,
As well as React students who aren't familiar with Vue?
Thanks for sharing videos with us 🙏
Thanks for the sharing
Hello. I also create programming courses. How can I submit my course in this channel ?
You can email beau@[channelName]
Oui Oui Monsieur!
exactly when I needed
Thanksss! I love supabase!
I have an application made with react js and Supabase I would like to know how I can make it so that the administrator profile can create, edit, update, delete seller type profile users, that is, so that seller type users can enter or authenticate in the application they have to be previously created by the administrator from their profile, the administrator provides the seller-type users with a name and password by another means, whether paper or other means, and the users enter the data provided by the administrator and if they are correct, they enter to your seller profile, how can I implement this functionality using only react js and Supabase, without needing to use Node js and express
Whats the difference between subscribe and real time?
I need this thanks for this
Nice❤
Does Superbase have function to ba a backend for budget tracking app? Thank you!
So I just finished the recovery password part, and that part is so bad, no one should follow it, this is a demo app which is fine i guess
Yeah, this is a bit disappointing. His Tailwind tutorial was excellent, but here he just kind of shows the ropes but very amateurishly
Thanks a lot!
uniqe fields like email are case sensitive how do i disable that?
Can you give more details about your app in this video?
How can I trigger policy on orders table? (37:50)
Please have app write full course too; thank you
Does it has automatic sources code
Never heard of it; is it better than firebase?
One big difference is that it uses relational DB than propriety noSQL. If you want that it's better.
Английский язык с французским акцентом намного понятней чем английский с британским акцентом 🙂
здравая тема
59:25
30:56
Instead of creating a tutorial for people who can't read what's in front of them, how about creating one where the supposed teacher explains why they're doing what they're doing... you know, how a tutorial is supposed to be?
Por los menos una traduccion en español por la pantalla
First❤
No I am the first 🥇
Why is supabase better ?
No
First view
supabase is a just another vendor lockin
Luckily it’s both cloud and offline implementation
🤔🤔🤔
French accent is soo cringe 🤣🤣🤣
Tell baguette to improve his English and presentation skills, and stop yapping.
Don't waste our time pls.