Fixing UUID Primary Key Error in Django

The error Field 'id' expected a number but got 'Other' suggests there might be an issue with how your database is handling the UUID field as a primary key. Here are some potential solutions:

Check Your Model Definition

Your model definition looks correct. The UUIDField with primary_key=True and default=uuid.uuid4 should automatically generate a UUID when creating new instances:

PYTHONCopied
class GMod(models.Model):
    id = models.UUIDField(
        primary_key=True,
        default=uuid.uuid4,
        editable=False
    )
    # other fields...

Possible Issues and Solutions

1. Missing UUID Import

Make sure you've imported the UUID module at the top of your file:

PYTHONCopied
import uuid
from django.db import models

2. Database Migration Issues

The error might be related to your database schema. Ensure you've properly migrated your database:

BASHCopied
python manage.py makemigrations
python manage.py migrate

3. Database Backend Compatibility

Different database backends handle UUIDs differently:

• PostgreSQL and MariaDB 10.7+ store UUIDs in a native uuid datatype
• Other databases store them as char(32)

If you're using PostgreSQL or MariaDB, make sure your database version supports UUID fields properly.

4. Explicitly Set the UUID

Try explicitly setting the UUID when creating the instance:

PYTHONCopied
import uuid

gmod = GMod(
    id=uuid.uuid4(),
    title=item['title_listing'],
    summary=item['overview'],
    genre_tags=item['g_tags'],
    ref_url=item['url'],
)
gmod.save()

5. Check for Existing Data

If you've added the UUID field to an existing model with data, you might need to follow the migration steps outlined in the Django documentation for adding unique fields to existing tables. This involves:

• Adding the field with null=True initially
• Populating existing rows with unique UUIDs
• Altering the field to make it non-nullable and unique

6. Check for Custom Save Methods

If your model has a custom save() method, ensure it's not interfering with the UUID generation.

Final Recommendation

The most likely issue is either a migration problem or a database compatibility issue. Try explicitly setting the UUID as shown in solution #4, and if that works, you can investigate further why the default value isn't being applied correctly.

If the problem persists, check your database logs for more detailed error messages that might provide additional clues about what's happening.