[Probably BUG] set_password and check_password accept values other than string as parameters

2020-03-11 Thread Dawid Czeluśniak
Hi all, I've noticed that both set_password and check_password methods accept values other than str as parameters. For example I'm able to set password to boolean values: In [1]: u.set_password(True) In [2]: u.save() In [3]: u.refresh_from_db() In [4]: u.check_password(True) Out[4]: True

Re: remove_stale_contenttypes doesn't remove entries for renamed apps.

2020-03-11 Thread Javier Buzzi
Hey guys, looks like gowtham added a new PR, can you guys add some insight? https://github.com/django/django/pull/12558 https://code.djangoproject.com/ticket/31123 The question of what to call the flag that will add this functionality has come up, I'm hoping one of you has a better name.

Re: Psycopg3 Redesign

2020-03-11 Thread Andrew Godwin
I am particularly excited for native async support arriving - that's something I'd love to have and ship support for from our side when it's done. The rest looks quite sensible too. Andrew On Wed, Mar 11, 2020 at 3:39 AM Jure Erznožnik wrote: > His proposed changes look awesome to me! > >

Re: Proposal for better managed raw SQL migrations

2020-03-11 Thread Adam Johnson
Hi Petr I too often end up managing some database objects like triggers, normally in order to support database migrations. I have always been happy using RawSQL migration operations though. What types of database objects are you mostly using? And how? I think django-migrate-sql is a neat idea,

Proposal for better managed raw SQL migrations

2020-03-11 Thread Petr Přikryl
I have only proposal for making Django migrations better handling raw SQL migrations. I like the way how django-migrate-sql do that https://github.com/festicket/django-migrate-sql. And it would be interested if Django has this feature build-in. We use a lot of raw SQL objects in our apps and

Proposal for better managed raw SQL migrations

2020-03-11 Thread Petr Přikryl
In our apps we have a lot of database objects which are hard to manage in classic Django migrations. Next, we clean our migrations time to time to speed up deployment process. And it would be awesome if Django would have system for raw SQL "models" and handle migrations and dependencies

Re: Psycopg3 Redesign

2020-03-11 Thread Jure Erznožnik
His proposed changes look awesome to me! IMHO, the biggest issue going async with current implementation was connection pooling for async code. I feared that we might need huge numbers of connections in certain scenarios, especially if the code required altering the connections themselves.

Psycopg3 Redesign

2020-03-11 Thread Asif Saif Uddin
Hi, As this library is used by django, I thought it would be good to share with django internals deveopers? https://www.varrazzo.com/blog/2020/03/06/thinking-psycopg3/ Hope it is useful. ./auvipy -- You received this message because you are subscribed to the Google Groups "Django