Google Mail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Message from discussion 1.2 - resolving the conflict between auto accessors and Doctrine_Record's methods
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Follow-up To:
Add Cc | Add Follow-up to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers that you hear
 
Adam Huttler  
View profile   Translate to Translated (View Original)
 More options 22 June, 20:27
From: "Adam Huttler" <adam.hutt...@fracturedatlas.org>
Date: Mon, 22 Jun 2009 15:27:36 -0400 (EDT)
Local: Mon 22 June 2009 20:27
Subject: RE: [doctrine-dev] 1.2 - resolving the conflict between auto accessors and Doctrine_Record's methods
As a practical matter, you can always define custom accessors/mutators for
just those fields. That's probably not what you're looking for, though.
> -----Original Message-----
> From: doctrine-dev@googlegroups.com [mailto:doctrine-
> dev@googlegroups.com] On Behalf Of eXtreme
> Sent: Monday, June 22, 2009 3:28 PM
> To: doctrine-dev
> Subject: [doctrine-dev] 1.2 - resolving the conflict between auto
> accessors and Doctrine_Record's methods

> 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
> any other way to resolve that conflict?


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google