which user?
a user usually is known during a request, while running the migration there
are no users, you can access all users the same way you may access all the
database, but this is not a user requested operation like a view processing
a template.
In any case you still may add/remove/modify
I tried from many locations
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to
After generating DB scheme, I need to add two rows with certain data to
certain table.
How to do it?
Can it be handled with migrations?
A complication is that these two rows contain strings dependent on the
user's language.
Can this be done?
--
You received this message because you are
Dear Django users,
I was playing a bit with migration squashing, and found that, after applying a
squashed migration (following the guide), stale records are left in the
migration history, which will prevent another migration to be applied with the
same name. This effectively results in a
Did you try run that code (django-admin startproject mysite) after changing
your system directory?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Do you tried run that code after changing your directory in cmd?
On Tuesday, October 4, 2016 at 4:37:03 AM UTC+5:30, new user wrote:
>
> followed the intro:
> https://docs.djangoproject.com/en/1.10/intro/tutorial01/
>
> when i run django-admin startproject mysite
>
> its prompt : "manage.py
It's a known issue: https://code.djangoproject.com/ticket/26760
On Tuesday, October 4, 2016 at 4:47:36 PM UTC-4, Kojedzinszky Richárd wrote:
>
> Dear Django users,
>
> I was playing a bit with migration squashing, and found that, after
> applying a
> squashed migration (following the guide),
had seen those answer's tried to uninstall it twice through pip .
also reinstalled the python
sure about the 1.10.2 version , the first step in the tutorial is to check
version
not using any virtualenv.
On Tuesday, October 4, 2016 at 5:02:12 PM UTC+3, Andromeda Yelton wrote:
>
> When I
Thank you Tim, the pointer was just I needed.
If anyone runs into this issue you will also need to update the auth_user
table to allow NULLs in the last_login date.
See this defect for details https://code.djangoproject.com/ticket/24679
--
You received this message because you are subscribed
I've uploaded the development repository of django-hotsauce-oauthclient
here:
https://bitbucket.org/tkadm30/django-hotsauce-oauthclient/
Regards,
Etienne
Le 2016-10-03 à 13:26, Etienne Robillard a écrit :
I'm trying to build a custom Django app with OAuth 2.0 support
through
https://docs.djangoproject.com/en/1.10/topics/forms/#looping-over-the-form-s-fields
That said, testing for Boolean vs. non-Boolean fields is really more logic
than belongs in a template. You can manually lay out the form in the
template, specifying where each field should go and surrounding them
When I copy-pasted the error message into Google I got some stackoverflow
posts saying that you can get this error if you have two different versions
of Django installed; are you certain that your 1.10.2 install is the only
one on your system?
On Mon, Oct 3, 2016 at 5:59 PM, new user
Try abstract base class , implement and you do the model works , make
composite pattern fine, after use django to this:
https://docs.djangoproject.com/en/1.10/topics/db/models/#abstract-base-classes
The base it's: in the composite object you overwrite method of simple
object.
Em
Do you tryied unninstall and install django again?
Are you using a virtualenv?
Em segunda-feira, 3 de outubro de 2016 20:07:03 UTC-3, new user escreveu:
>
> followed the intro:
> https://docs.djangoproject.com/en/1.10/intro/tutorial01/
>
> when i run django-admin startproject mysite
>
> its
Answering to myself obviously sqlmigrate can't really do anything with code
in RunPython.
So I suspect the biggest problem would be something like this:
- early data migration that uses an initial schema a certain model
- a later schema migration that changes that
so trying to generate the SQL
Related to this other thread:
https://groups.google.com/forum/#!msg/django-users/V8Ei2qZJ8VI/bFUeY2wTAQAJ;context-place=forum/django-users
I'm working on trying to find a workaround for migrations killing our
local/CI servers, until there is a better fix in Django stable..
So started this
python 2.7.10
django 1.10.2
i think its what is says here:
https://code.djangoproject.com/ticket/18296
but i cant solve it
On Tuesday, October 4, 2016 at 5:19:59 AM UTC+3, Sylvain Dégué wrote:
>
> What Django & python version do you have?
>
> Le lundi 3 octobre 2016 19:07:03 UTC-4, new
17 matches
Mail list logo
