Re: Getting rid of get_db_prep_lookup on Field subclasses?

2008-07-15 Thread Leo Soto M.
On Tue, Jul 15, 2008 at 12:38 PM, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > > On Tue, 2008-07-15 at 11:49 -0400, Leo Soto M. wrote: >> After fixing some corner cases of #7560[1], and realizing that it is >> too easy to write a wrong get_db_prep_lookup method (example: >> #7448[2]), I have

Re: Getting rid of get_db_prep_lookup on Field subclasses?

2008-07-15 Thread Malcolm Tredinnick
On Tue, 2008-07-15 at 11:49 -0400, Leo Soto M. wrote: > After fixing some corner cases of #7560[1], and realizing that it is > too easy to write a wrong get_db_prep_lookup method (example: > #7448[2]), I have reached the conclusion that there is no reason to > have *two* methods for doing the

Getting rid of get_db_prep_lookup on Field subclasses?

2008-07-15 Thread Leo Soto M.
After fixing some corner cases of #7560[1], and realizing that it is too easy to write a wrong get_db_prep_lookup method (example: #7448[2]), I have reached the conclusion that there is no reason to have *two* methods for doing the python -> db conversion (``get_db_prep_save`` and