On Tue, 2006-10-10 at 15:48 -0700, Beau Hartshorne wrote:
> extra() expects a dictionary of extra select fields, and a list of
> query parameters to go with it. Since dictionaries are unordered,
> something like this fails:
>
> extra(select={'thingOne': 'REGEX %s', 'thingTwo': 'REGEX %s'}, params
> = (one, two))
>
> Is this a known problem? Should I be writing my own SQL query instead
> of trying to make extra work?
Looks like you're right; there is going to be a problem there. The
"params" attribute is typically more useful with extra "where" clauses,
which is a list, so this doesn't come up in that case.
Could you file a ticket about this, please, so that we don't forget
about it forever.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
