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 7977447
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 4, 20262026-06-04T09:12:07+00:00 2026-06-04T09:12:07+00:00

My models.py includes several fields. The primary key is by default, set automatically by

  • 0

My models.py includes several fields. The primary key is by default, set automatically by Django.

I have a Django crontab that attempts to update each entry on a regular basis, but can no longer save. (Until recently, I had manually set the primary key based on one of these fields.)

Could someone suggest how to get around this. For each entry, I’d like to be able to update each of the declared fields and create if non-existent.

I was under the impression that save does both create or update as neccessary

class ABC(models.Model):
    init = models.CharField(max_length=6)
    last = models.CharField(max_length=20)
    fullid = models.CharField(max_length=30) <--- used to be primary_key=True

Crontab (pseudocode)
    for x in list:
        try: 
           entry = init='abc', last='def', fullid='xyz'
           entry.save()

        except: 'unable to update.' <-- I'm now hitting the except all the time.
  • 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-06-04T09:12:09+00:00Added an answer on June 4, 2026 at 9:12 am

    Use something like that:

    try: 
        abc = ABC.objects.get(fullid=id) 
    except ABC.DoesNotExist: 
        ABC.objects.create(params)
    else:
        abc.field = value
        abc.save()
    

    Never ever use try: ... except: ... because this way you don’t even know what have failed inside. Catch only “awaited” exceptions which you do know how to process. Or, if you want it to be bulletproof and unstoppable – at least display catched exception info.

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

Sidebar

Related Questions

I have several models that includes nested classes and lists. Many of the class
I'd like to create a form that includes fields from two separate models, along
I have set up a Core Data model that includes an entity, Item with
For several reasons that I don't have the liberty to talk about, we are
I have the following in several of my models: The Poll.rb for instance: def
I have a DB model that uses several tables to hold business logic data;
What's the rails way to see posts nested beneath several associative models that a
I would like to have functionality shared by several models to be abstracted into
I'm using rails-rspec gem and I have several specs (models, controllers, etc). When I
I have several different types of data involving date range that I want to

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.