hell, man, it was so difficult from the start, but it took me only one day to integrate your logic to my small flask project and create and use data from different tables. Now it looks so easy. like hiking - watching it from the top to the bottom and seeing where I started. thank you, really helpful video
Hi, thank you so much for these videos, I love the way you teach them and I am really thankful for them. Pls, would you be kind to do one on authentication, authorization and jwt?
I learn abit about db relationship here even if that wasnt the content ^^ I have one question, about db relationship. I see normally people links it with "id". And I also see that it requires user intervention to link the relationship in most guides. But if I already have a structure that you dont need to manually link the relationship, and just the code should take care of it. For example, I have a table with assets that contains Serialnumber as uniqe value. Then I have another table with for example accesories, also contains asset serialnumber but possible of duplicates. To link these two tables, should be done in 1-to-many relationship? And I want it to match the relationship by Serialnumber. Where does the code come iin, that does the "action" to link the relationships. ^^ Or is it better do use a different way? Like join or filter?
Would you save this first form to the database if this had multiple views on the same route. For instance, the application TYPE FORM. It allows you to answer questions via multiple fields while changing views for each question field. I assume they don't save the fields until all the fields are submitted. Thoughts?
You'll need a way to keep track of the answers selected in the previous views. Saving to the database in a temporary table or partially filling the main table is the most straightforward way of doing that. Other ways are keeping the answers in the browser session or inside of a session on the server (which acts like another database).
i'm first who comment , i hope to see a video about how to make flask in heigh performance level pypy , asynchronous , gunicorn .... , please make it 😭😀😂🌹🔥
hell, man, it was so difficult from the start, but it took me only one day to integrate your logic to my small flask project and create and use data from different tables. Now it looks so easy. like hiking - watching it from the top to the bottom and seeing where I started. thank you, really helpful video
Man, thank you so much!
Hi, thank you so much for these videos, I love the way you teach them and I am really thankful for them. Pls, would you be kind to do one on authentication, authorization and jwt?
I have a video on JWT already, but it might be time for a new one. I'll see what I can do.
I learn abit about db relationship here even if that wasnt the content ^^
I have one question, about db relationship. I see normally people links it with "id".
And I also see that it requires user intervention to link the relationship in most guides.
But if I already have a structure that you dont need to manually link the relationship, and just the code should take care of it.
For example, I have a table with assets that contains Serialnumber as uniqe value.
Then I have another table with for example accesories, also contains asset serialnumber but possible of duplicates.
To link these two tables, should be done in 1-to-many relationship? And I want it to match the relationship by Serialnumber.
Where does the code come iin, that does the "action" to link the relationships. ^^
Or is it better do use a different way? Like join or filter?
by the way for people who will try it, it's "prefix_label" now not "prefix"
👏👏👏👏can you upgrade code to have dropdown field with checkboxes?
I'll consider doing that, but if you want it for your app, you just replace the default widget with a radio widget for your SelectField.
hey how can i divide this code into multiple pages
Would you save this first form to the database if this had multiple views on the same route. For instance, the application TYPE FORM. It allows you to answer questions via multiple fields while changing views for each question field. I assume they don't save the fields until all the fields are submitted. Thoughts?
You'll need a way to keep track of the answers selected in the previous views. Saving to the database in a temporary table or partially filling the main table is the most straightforward way of doing that. Other ways are keeping the answers in the browser session or inside of a session on the server (which acts like another database).
is it a new way to do many-to-many, i see it's different from what you did in an old video
i'm first who comment , i hope to see a video about how to make flask in heigh performance level pypy , asynchronous , gunicorn .... , please make it 😭😀😂🌹🔥
That's a good idea I haven't considered. I'll see what I can do.
Dope
Thanks for watching!