#psycopg2 — Public Fediverse posts

djangoでUniqueViolationの例外エラーを取得する
https://qiita.com/naito_neegi/items/d29bfbcea8cbb71f41bf?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #Python #Django #エンジニア #psycopg2 #新卒エンジニア

@veronica #sqlalchemy has been nothing but trouble in our team. Lazy loading makes you have more transactions that last longer and also leads to the n+1 query problem. And I hate the query constructor to me it’s harder to understand than plain old SQL. We’re stripping it off to get back down to the #psycopg2 layer.

@veronica #sqlalchemy has been nothing but trouble in our team. Lazy loading makes you have more transactions that last longer and also leads to the n+1 query problem. And I hate the query constructor to me it’s harder to understand than plain old SQL. We’re stripping it off to get back down to the #psycopg2 layer.

@scy no it doesn’t help with migrations, so it probably doesn’t solve your problem. I knew that when I responded. I should have said more, especially that. The reason I answered, and the reason I answered with this is that we were on #sqlalchemy and it’s done nothing but get in the way. #psycopg2 was underneath and now we’re using that and life is much better. So that’s what I *prefer* though I’m sorry it’s not what you need.

@scy no it doesn’t help with migrations, so it probably doesn’t solve your problem. I knew that when I responded. I should have said more, especially that. The reason I answered, and the reason I answered with this is that we were on #sqlalchemy and it’s done nothing but get in the way. #psycopg2 was underneath and now we’re using that and life is much better. So that’s what I *prefer* though I’m sorry it’s not what you need.

@scy #psycopg2

@scy #psycopg2

Probably I need #psycopg2. #Python

不正アクセスしてきたホストの国コードを知ってセキュリティ対策に活用する
https://qiita.com/pipito-yukio/items/147f7b2f42ad9fc1dbd0?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #Python #Linux #PostgreSQL #Docker #psycopg2

Are you a #Django developer using a #celery job queue and #psycopg2-binary on #applesilicon ?

I'm deploying to Heroku which requires the binary, hence using it also in development.

Have you moved to psycopg2-binary v2.9.6?

If so, do you also have the problem where the celery worker falls over on the first interaction with the Django ORM? I get it on 2 different computers, but not on Intel.

My problem report: https://github.com/psycopg/psycopg2/issues/1593

Any thoughts on what might be going on?

@felixxm @carlton

Dear #Python community,

what is the recommended library to interact with #PostgreSQL?
I've heard of #psycopg2 and #SQLAlchemy in context of web applications but want to build a desktop app.
Tried #PonyORM with mixed results.

I'd prefer not to go raw #SQL if possible.

Dear #Python community,

what is the recommended library to interact with #PostgreSQL?
I've heard of #psycopg2 and #SQLAlchemy in context of web applications but want to build a desktop app.
Tried #PonyORM with mixed results.

I'd prefer not to go raw #SQL if possible.