Re: Django : Change Backend as mysql and create sample example using django ORM

Hi Sonali, Could you please paste the models.py file ?? Might be there is some syntax error in the models you have created. Regards, Raghav On Tue, Aug 28, 2018 at 9:41 PM parmeshwar deharkar < parmeshwardehar...@gmail.com> wrote: > hi sonali > you install sql libray in your project package

Re: Not Creating test DBs with PG backend

On 08/28/2018 08:33 PM, Tim Graham wrote: Why is a new option needed? Why can't --keepdb be used for this use case? Because that would be different behavior. If you can convince me that using --keepdb is a solution, then I will use your argument to say that --keepdb should be on always.

Re: Django Channels doesn’t conform to Django middleware specifications

Just to say that I've reopened the original issue in question as it's clear now this needs to be fixed. I won't be able to get to writing a fix for a bit, though, so if someone else wants to they should. Andrew On Tue, Aug 28, 2018 at 5:41 AM John Obelenus wrote: > Just finished reading both

Re: Django : Change Backend as mysql and create sample example using django ORM

hi sonali you install sql libray in your project package then edit the setting.py file at django framework with database . I hope your problem will be solve... On Mon, Aug 27, 2018 at 4:54 PM Sonali Vighne wrote: > Hi, > I have tried a lot to change Django back-end as MySQL but not able to >

Re: Help wanted testing proposal for the Migration Graph algorithm

Hi Carlton, Adam asked me to take a look at this. I've run it on our codebase with ~1100 migrations and ~380 apps. Running on Django 2.1, the results of this script (the updated version) are: > 1min 23s ± 1.1 s per loop (mean ± std. dev. of 7 runs, 1 loop each) Running on the branch,

Re: Django Channels doesn’t conform to Django middleware specifications

Just finished reading both bug reports and I see the file loader lookup in whitenoise. This explains a lot actually. We are still on Channels 1, and when we tried an upgrade to Channels 2, but encountered terrible performance at load and had to undo it. On Tuesday, August 28, 2018 at 8:00:17

Re: Django Channels doesn’t conform to Django middleware specifications

Can I ask a dumb question? Why did you only discover this with adding Whitenoise, and not the default/common middleware stack that comes in django? Asking that question in another way: What is specific to whitenoise that this constant loading of middleware causes such a perf hit? This question

RE: Django : Change Backend as mysql and create sample example using django ORM

I will paste full error and stack trace here. This is occurred when I am giving “python manage.py migrate” command Operations to perform: Apply all migrations: admin, auth, contenttypes, sessions Running migrations: Traceback (most recent call last): File

Re: Not Creating test DBs with PG backend

Why is a new option needed? Why can't --keepdb be used for this use case? On Tuesday, August 28, 2018 at 2:23:52 AM UTC-4, Curtis Maloney wrote: > > Greetings, > > one problem that turns up more and more frequently, it seems, is that > someone is trying to run tests but can't because of the

Re: Privacy in Django (GDPR)

I outlined the problem of parent domain cookies included in Django's error reports, which may be a problem due to GDPR. There's a ticket in the Django bugtracker: https://code.djangoproject.com/ticket/29714 And a discussion in the 'developers' group:

Not Creating test DBs with PG backend

Greetings, one problem that turns up more and more frequently, it seems, is that someone is trying to run tests but can't because of the following scenario: 1. The user they connect to the DB using a role that does NOT have permission to create a DB 2. Django's PG adapter, when keepdb is