Hi Alparslan, This totally makes sense, and specially because __g__dirty is an internal field, and users shouldn't be given tools to bad things ;) If you put a patch for this, I will happily review it.
Renato M. 2014-05-02 13:08 GMT+02:00 Alparslan Avcı <[email protected]>: > Hi folks, > > In auto-generated persistent classes, we create an array field called > _ALL_FIELDS as you know. But this array also contains __g__dirty field, > which is not a stored field at all. Maybe we should remove __g__dirty field > from the array, since the array is used for getting all fields in the > stored table. We can also remove it from Field enum, so the users do not > know about the __g__dirty field. > > Wdyt? > > Thanks. > > > -- > Alparslan Avcı >
