Hi Mark,
On Sat, Apr 7, 2012 at 8:57 PM, Mark Phillips wrote:
> Actually, just an ORDER BY FK, PK would produce the above... GROUP
>> BY would be used if you need something like counts/avg for each FK set.
>>
>
> I agree that if the data in the db was entered correctly in the first
> plac
Hi Timothy,
Assuming as an example that 0002_<>.py is the migration that you have
already applied to production server, this is the scheme I follow:
- Make sure you have your local db up to date i.e. all the model changes
have been applied to database.
- Fake a reversal to the last migra
This looks fine. Are there any errors in the web server logs?
Regards,
Abhaya
On Mon, Apr 27, 2015 at 10:23 PM, dk wrote:
> we decided to test django 1.8, using python manage.py runserver works
> great. but now the production wsgi stop working,
> I remember there was a change between version
On Tue, Apr 28, 2015 at 9:40 PM, dk wrote:
> I check the apache httpd log and do get this
>
> [Tue Apr 28 10:33:49.982311 2015] [:error] [pid 18060] [client
> 10.35.0.91:61408] from django.apps import apps
> [Tue Apr 28 10:33:49.982336 2015] [:error] [pid 18060] [client
> 10.35.0.91:61408] I
4 matches
Mail list logo