No problem. Still you can provide an one off value by selecting option 1
and migrate. It won't have any impact.
I think this warning will arise on every occasion we alter the table
structure irrespective of entry being there or not.
On 04-Aug-2015 11:05 am, "sarfaraz ahmed" wrote:
> I have entri
I have entries present in User Profile Table. But this field belongs to
User_Address model which is new and does not have any entries present.
Please advice.
On Tue, Aug 4, 2015 at 12:51 AM, rajan santhanam
wrote:
> Hi Ahmed,
>
> This message is because you hav few entries already present for
Hi Ahmed,
This message is because you hav few entries already present for that model
in DB. If it is OK for you, you can add datetime.now as default value for
the existing rows
Many Thanks
Rajan
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
I missed the pastebin link in my last post. Sorry...
Here is the model code
http://pastebin.com/5EF1hV8U
On Tuesday, 4 August 2015 00:48:18 UTC+5:30, sarfaraz ahmed wrote:
>
> Hello Team,
>
> I have a model and I have added two fields to User_Address model
> creation_date and updation_date. I h
Hello Team,
I have a model and I have added two fields to User_Address model
creation_date and updation_date. I have pasted the model code at pastebin.
Please take a look.
I am getting following error while running makemigrations command
You are trying to add a non-nullable field 'creation_d
5 matches
Mail list logo
