Re: Field lookup types and backwards incompatibility

I thought Django already did option 1. If it doesn't, why not? What are the possible edge cases? Using a date field named "date" as a foreign key to another model that also contains a "date" field? On May 10, 1:47 am, Ulrich Petri wrote: > Currently there are at least 4 open

Re: Field lookup types and backwards incompatibility

On 05/11/2011 03:17 AM, Chris Beaven wrote: 3. Change lookups to be uppercase (start the process of deprecating the current lowercase ones) uagh, .filter(foo_CONTAINS=bar)? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to

Re: Field lookup types and backwards incompatibility

3. Change lookups to be uppercase (start the process of deprecating the current lowercase ones) -- 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

Field lookup types and backwards incompatibility

Currently there are at least 4 open tickets [1-4] that propose the addition of new lookup types. Two of them [1,2] are in DDN because of backward compatibility concerns. Following that (IMHO valid) logic makes it impossible to _ever_ add new lookup types to django without breaking backwards