After thinking about my question for a while, I’ve decided it’s dumb. :P The part I was thinking about has more to do with WO’s Key-Value-Coding, not so much the ORM. Your solution is the way I’ll go.
-Lon On Wed, May 18, 2016 at 4:40 PM, Aristedes Maniatis <a...@maniatis.org> wrote: > On 19/05/2016 7:03am, Lon Varscsak wrote: > > Hey guys, I know about insert/update/delete validation routines, but is > > there a way to write validations for specific attributes so that when > > someone tries to push a value into a property it could be rejected? I > know > > that WO/EOF (Maybe Wonder) had something like this where I could write > > validateMyAttribute methods. > > That would be easy to write in the model class. Just override the setter > and add your own logic. > > is that what you had in mind? > > Ari > > > > -- > --------------------------> > Aristedes Maniatis > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A >
