RuntimeError: Working outside of application context.

[Omar Mahhmoud]

when i am running the code, i got this error.

RuntimeError: Working outside of application context.

This typically means that you attempted to use functionality that needed
the current application. To solve this, set up an application context
with app.app_context(). See the documentation for more information.

Notice that i had to change the sqlalchemy loading to the following code
app.config["SQLALCHEMY_DATABASE_URI"] = "postgresql:///quokka"

and i tried to add app.app_context() after db = SQLAlchemy(app)
but still, the error is raised in all threading process

Any solutions for this ?

[Chuck Black]

Hi Omar, My apologies, it has been a really long time since I was in that SQL code for quokka. Are you attempting to follow the 52-weeks-of-python course, or trying to run quokka? If you are interested in the 52-weeks-of-python course, I'd recommend you perhaps scrap the SQL stuff - postgres can be a bear to get installed and operating correctly if you don't have too much experience with it. I've found Mongo to be much easier, and I use it exclusively in the quokka-prime stuff. If you are set on getting SQL to work, I might recommend using sqlite3, which is a simpler database and allows you to get your feet wet with SQL, without having to go the full postgresql or mysql route. Regarding that error - I have never seen that before, "working outside of application context". As I'm currently working full-time and don't really have time to try to recreate your situation - sorry! Good luck, whatever path you choose! --- chuck

…

On Fri, Jun 9, 2023 at 8:09 PM Omar Mohamed Ahmed ***@***.***> wrote: when i am running the code, i got this error. RuntimeError: Working outside of application context. This typically means that you attempted to use functionality that needed the current application. To solve this, set up an application context with app.app_context(). See the documentation for more information. Notice that i had to change the sqlalchemy loading to the following code app.config["SQLALCHEMY_DATABASE_URI"] = "postgresql:///quokka" and i tried to add app.app_context() after db = SQLAlchemy(app) but still, the error raised in all threading process — Reply to this email directly, view it on GitHub <#21>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APKL7FUPAAWINCXPMI52QWDXKPQNLANCNFSM6AAAAAAZBMKYUE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Omar Mahhmoud]

Thanks for your prompt response, i will try to use SQLite to get it run

[Dilan-Peiris]

Apparently as of Flask-SQLAlchemy 3.0, all access to db.engine (and db.session) requires an active Flask application context. db.create_all uses db.engine, so it requires an app context, i also tried to push application context, but it raised the same errors on the threads.
Instead i required pip to install packages that was released in the time of development.

pip install Flask==2.1.1 pip install Flask-SQLAlchemy==2.5.1

fixed the issue.

[Chuck Black]

Glad you figured it out and got it fixed! I admit I haven't been in sql alchemy for a number of years, so it is good that you were able to dig down and find the solution - always one of the most satisfying things, when it finally works!

…

On Tue, Jan 2, 2024 at 8:11 AM Dilan-Peiris ***@***.***> wrote: Apparently as of Flask-SQLAlchemy 3.0, all access to db.engine (and db.session) requires an active Flask application context. db.create_all uses db.engine, so it requires an app context, i also tried to push application context, but i also raised errors on the threads. Instead i required pip to install packages that was released in the time of development. pip install Flask==2.1.1 pip install Flask-SQLAlchemy==2.5.1 fixed the issue. — Reply to this email directly, view it on GitHub <#21 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APKL7FQT5NYEPIDSTW5YFCDYMQWURAVCNFSM6AAAAAAZBMKYUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZUGIZDQNRYGA> . You are receiving this because you commented.Message ID: ***@***.***>