Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#12453 closed (invalid)

Possible bug with multi-db changes

Reported by: Sean Brant Owned by: nobody
Component: Uncategorized Version: dev
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I posted this on the mailing list and Russ suggested I open a ticket. The mailing list message can be view here <http://groups.google.com/group/django-developers/browse_thread/thread/ce8e7536e34611f6>.

I have attached a test project and app that will show the failure I'm receiving.

Looks like its a combination of ModelAdmin inline, ImageField and a ManyToMany with a through model.

Attachments (1)

testmultidb.zip (7.7 KB ) - added by Sean Brant 15 years ago.
Sample project that causes failure

Download all attachments as: .zip

Change History (4)

by Sean Brant, 15 years ago

Attachment: testmultidb.zip added

Sample project that causes failure

comment:1 by Sean Brant, 15 years ago

Version: 1.1SVN

I should also note how to produce the error.

Go to http:127.0.0.1:8000/admin. Then add a new Account, making sure you select an image. When saving you should get an error similar to this one (http://dpaste.com/138130/).

comment:2 by Sean Brant, 15 years ago

Resolution: invalid
Status: newclosed

This is no longer causing problems for me. So either some other fix corrected it, or most likely I was doing it wrong. I'm marking as invalid.

comment:3 by Russell Keith-Magee, 15 years ago

If it makes you feel any better, I was able to verify that this problem did exist at the time you reported it. However, I agree that this now appears to be fixed.

Note: See TracTickets for help on using tickets.
Back to Top