> I see that the Oracle backend already includes > OracleQueryconvert_values which does conversion into the backend based > on the the passed value and the field type. > > Perhaps we need to add that for PostgreSQL now? It's pretty onerous > to do the casting at the app level. >
The `convert_values` routine is only used on values coming _from_ the database (via `resolve_columns`), and not on values going _to_ the database. I'm with Malcolm on not supporting this feature of automatically casting to string because the database is doing the "right thing" here. [1] However, I believe there are still parts of Django that depend on this behavior -- for instance adding a search field to a related field in the admin is one of these situations (I need to provide specifics, but don't have it on hand at the moment). [1] See http://groups.google.com/group/django-developers/browse_frm/thread/371e8743fffd3d0c. See also: http://code.djangoproject.com/ticket/6523. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
