Комментарии:
it is still useful after 3 years. Miguel you are my hero.
ОтветитьMany thanks!
ОтветитьValueError: Constraint must have a name what is this error?
ОтветитьVery good video, it helped me a lot. New subscriber.
ОтветитьGreatest tip
ОтветитьIt seems that this option this option render_as_batch=True needs to set a naming convention for constraints (e.g. metadata = MetaData(naming_convention=convention) and db = SQLAlchemy(app, metadata=metadata)) to avoid errors of the type ValueError: Constraint must have a name (for example when columns are defined with unique=True), right?
ОтветитьAmazing! Thank you very much.
ОтветитьExcelent, thanks a lot. I see that you like to use flask, what do you think about to use flask vs django?
ОтветитьAmazing! I had this problem days ago hahahaha
ОтветитьThanks so much. I was ready to give up on my project because of this and you made the process seem so simple. You've got a new subscriber!
ОтветитьHow to create a global counter variable in flask which will be incremented in every request?
Ответитьmany thanks
ОтветитьThank you Miguel,I run into this during the microblog project and change the dev db to postgresql since this going to the "prod" version.. BTW, the flask mega tutorial is a wonderful course!
ОтветитьThanks! And just in time to save a local project from having to migrate to MySQL
ОтветитьVery informative video.
Ответить