Message from discussion
1.2 - resolving the conflict between auto accessors and Doctrine_Record's methods
MIME-Version: 1.0
Received: by 10.151.136.10 with SMTP id o10mr961807ybn.22.1245698855027; Mon,
22 Jun 2009 12:27:35 -0700 (PDT)
Date: Mon, 22 Jun 2009 12:27:35 -0700 (PDT)
X-IP: 84.38.85.66
User-Agent: G2/1.0
X-HTTP-UserAgent: Opera/9.80 (Windows NT 5.1; U; en) Presto/2.2.15
Version/10.00,gzip(gfe),gzip(gfe)
Message-ID: <758a4f2c-97bc-476b-ac05-2b03c1cf1cfe@l12g2000yqo.googlegroups.com>
Subject: 1.2 - resolving the conflict between auto accessors and
Doctrine_Record's methods
From: eXtreme <jacek.jedrzejew...@gmail.com>
To: doctrine-dev <doctrine-dev@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Doctrine supports a cool feature called "auto accessor override".
AFAIR this feature wasn't planned before 1.0, that's why there is a
"small" problem now in 1.0 and 1.1, which is possible to be
(partially?) fixed in new 1.2 branch (I hope so).
I'm talking about get* and set* functions in Doctrine_Record and
Doctrine_Record_Abstract. They reserve some names, which cannot be
used as model's fieldnames, because everything goes crazy - they
conflict with magic and custom get* and set* function of auto
accessors. I heard many complains >>why does doctrine crash when I add
"data" field in my model<< (for example for session storage). And
there is no info anywhere, that it is impossible to have "data",
"last" or "last_modified" fields in doctrine with auto accessors or in
symfony.
I'm aware that renaming all get* and set* is a big backward
compatibility breaker, so I won't dare to propose that. :P Is there
|
