On Sunday, July 28, 2019 at 2:35:03 PM UTC-7, David Grant wrote:
>
>
> I'm using Google AppEngine and I have no access to the server. The
> alternative is to have the exact same code checked out on my local machine.
> Connect to the remote database with a special proxy tool that google
>
On Sunday, July 28, 2019 at 10:10:57 AM UTC-7, James Schneider wrote:
>
>
>
> On Sun, Jul 28, 2019, 12:47 AM David Grant > wrote:
>
>> Anyone see any problems with running migrations in Middleware?
>>
>
> What's the actual problem you are trying to solve by doing this? This is a
> bad idea for
The reason I want to do this by the way, is because I'm using Google
AppEngine and I have no access to the server. The alternative is to have
the exact same code checked out on my local machine. Connect to the remote
database with a special proxy tool that google provides (so the db becomes
On Sun, Jul 28, 2019, 12:47 AM David Grant wrote:
> Anyone see any problems with running migrations in Middleware?
>
What's the actual problem you are trying to solve by doing this? This is a
bad idea for a number of reasons, and I can't think of any good ones.
-James
>
--
You received this
Yes, I do see several problems. Some of them:
- All middleware are run for every request
- What you're doing can slow down your request response time to minutes,
depending on home many migrations you have
- Depending on your database, migrations might not be atomic thus causing
conflicts
- You
Anyone see any problems with running migrations in Middleware?
import logging
import os
import time
from django.core.management import call_command
from django.http import HttpResponse
from products.models.models import AppVersion
LOG = logging.getLogger(__name__)
# Used for testing locally
6 matches
Mail list logo
