MultipleObjectsReturned: get() returned more than one Address -- it returned 5! about django-address HOT 7 CLOSED

I am also seeing duplicate looking address entries in my address table. Not sure if this is the cause or an effect. I see at least 2 more on the same page as well.

from django-address.

Thanks for the report, I'll look in to it first thing this morning.

from django-address.

Hi again John,

Okay, firstly, yep, it's the duplicate addresses that are causing the problem. I've updated the code to prevent the error and use one of the existing duplicates (and prints a verbose warning). Your users should be able to enter addresses that have duplicates now.

I ran a bunch of tests and it looks like the code does prevent duplicates after migrations have been run. This indicates the duplicates were most likely introduced during your initial migration. I'll need to analyse the migration code and figure out where this is happening to prevent it occurring again for other migrations.

In the mean time, I'll write a helper piece of code to assist in removing duplicates, but you'll need to your own hook into the code so we can update any other models you may have that refer to the duplicates. I'll keep you posted.

Cheers,
Luke

from django-address.

Hi Luke,

I'm now using the head on develop and it appears to have fixed this issue.

Two questions:

1. Also, any update on that piece of helper code?
2. Do you think we'll be on master in the foreseeable future?

thanks!
John

from django-address.

Hi John,

Sorry, I haven't looked at the helper code yet. :( I'll hopefully get some time to take a look over the next week or two.

I've been thinking of splitting the develop branch off into a separate repository. It's diverged quite a lot from the master branch, and I'm not sure I should force users into moving to what is a very different system.

Cheers,
Luke

from django-address.

No problem, I don't think the current (unmerged status) is causing any problems.

What you're suggesting is a major version change with a migration path or a completely separate project with no migration path? My only concern would be creating more independent projects that you are trying to maintain in your limited time, but I can see how it could be less work overall.

from django-address.

Since the underlying issue related to this is handled, closing this. I do see the additional references to the dev vs master situation.

from django-address.