And rewrite it in every project?! No, thanks. I'd like to write it now
and have no troubles in future at all.
On Jun 2, 9:12 am, "Leo Soto M." <[EMAIL PROTECTED]> wrote:
> On Wed, May 28, 2008 at 5:08 PM, Alex Koshelev <[EMAIL PROTECTED]> wrote:
> > On May 29, 12:57 am, "Leo Soto M." <[EMAIL
On Wed, May 28, 2008 at 5:08 PM, Alex Koshelev <[EMAIL PROTECTED]> wrote:
> On May 29, 12:57 am, "Leo Soto M." <[EMAIL PROTECTED]> wrote:
>> I see that almost all Field subclasses which implements
>> get_db_prep_save end calling Field.get_db_prep_save anyway. That's
>> curious, because
Today it may be empty, but tomorrow there can appear some useful code.
So I think its better to follow that style.
On May 29, 12:57 am, "Leo Soto M." <[EMAIL PROTECTED]> wrote:
> I see that almost all Field subclasses which implements
> get_db_prep_save end calling Field.get_db_prep_save anyway.
I see that almost all Field subclasses which implements
get_db_prep_save end calling Field.get_db_prep_save anyway. That's
curious, because Field.get_db_prep_save is a no-op.
Is it just some OOP style which we want to keep?
--
Leo Soto M.
http://blog.leosoto.com
