Opened 18 years ago

Closed 18 years ago

Last modified 18 years ago

#963 closed defect (duplicate)

Save not working with non-integer foreign keys

Reported by: jsprinklex9@… Owned by: Adrian Holovaty
Component: Database layer (models, ORM) Version:
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Hi Django Project. First off, Django rocks! However I ran into a little problem recently. I have a model with non-integer foreign keys (using strings - codes, etc.), and doesn't work because in fields.get_db_prep_save() the return statement says int(value). This appears to be a recent change, either late last week or early this week I think. Anwyay, that's my take on it, but you may have very good reasons for whatever the change was that is causing this behavior.


Change History (2)

comment:1 by jsprinklex9@…, 18 years ago

Alright, this is probably a duplicate of ticket #927. Sorry about that.

comment:2 by Jacob, 18 years ago

Resolution: duplicate
Status: newclosed

Duplicate of #927.

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