Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6864835
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T02:57:46+00:00 2026-05-27T02:57:46+00:00

Originally, the model attribute location for Item class was defined like the following: location

  • 0

Originally, the model attribute location for Item class was defined like the following:

location = models.ForeignKey('Location', related_name='+', null=True, on_delete=models.SET_NULL)

It then got redefined to:

location = models.ForeignKey('Location', related_name='+', on_delete=models.PROTECT)

Because of the change in definition, I executed South’s schemamigration. South responded with

The field ‘Item.location’ does not have a default specified, yet is
NOT NULL. Since you are making this field non-nullable, you MUST
specify a default value to use for existing rows.

I picked choice ‘2’ and provided the PK (integer) of an existing Location.

But when I ran migrate, I got the following error:

django.db.utils.IntegrityError: column “location_id” contains null values

I don’t understand why I got this error when I had provided a valid default location PK. This is really mind-boggling. Please help~ Thanks.

Migration spec:

def forwards(self, orm):
    # Changing field 'Item.location'
    db.alter_column('lend_borrow_item', 'location_id', self.gf('django.db.models.fields.related.ForeignKey')(default=11, to=orm['app_name.Location']))
def backwards(self, orm):
    # Changing field 'Item.location'
    db.alter_column('lend_borrow_item', 'location_id', self.gf('django.db.models.fields.related.ForeignKey')(null=True, to=orm['app_name.Location']))

models = {
    'app_name.location': {
        'Meta': {'ordering': "['name']", 'object_name': 'Location'},
        'id': ('django.db.models.fields.AutoField', [], {'primary_key': 'True'}),
        'name': ('django.db.models.fields.CharField', [], {'max_length': '20'})
    },
    'lend_borrow.item': {
        'Meta': {'object_name': 'Item'},
        'id': ('django.db.models.fields.AutoField', [], {'primary_key': 'True'}),
        'location': ('django.db.models.fields.related.ForeignKey', [], {'related_name': "'+'", 'to': "orm['app_name.Location']"}),
        'name': ('django.db.models.fields.CharField', [], {'max_length': '50'})
    }
}
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T02:57:46+00:00Added an answer on May 27, 2026 at 2:57 am

    This problem seems to be caused by South Defect #627

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a model and form like so: class Image(BaseModel): original = db.BlobProperty() class
In Data Model of the reference, writer spent lots of effort explaining how User-defined
I have the following model: And I want the user to be able to
I have got an existing Rails project (Rails 2.3.8) and I got following Model
There is model call Event which contains following attributes start_at, end_at, details, trainer This
I have a ActiveRecord Car model: class Car < ActiveRecord::Base def check_value puts self.load_size
i have three models, all for a has_many :through relationship. They look like this:
I have a User model that has a :credits attribute. I want a simple
I have a Model called Todo.rb which has an attribute called asset which is
I have a Rails model with various attributes and has_many relationships to other models.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.