On Tue, 2009-11-24 at 20:54 -0800, Mario Briggs wrote: > Instead we will let users run into errors when they do a '=' compare > of a Django Text type, and then let them ponder whether they need that > column as a CLOB in the backend.
Shouldn't something be changing that = into a LIKE (and escaping LIKE metacharacters in the parameter)? I don't know why a user should have <queryset>.filter(object_id='1') fail, as that breaks the ORM abstraction. Maybe that's not what you're suggesting? Richard
signature.asc
Description: This is a digitally signed message part
