[
https://issues.apache.org/jira/browse/GORA-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Renato Javier Marroquín Mogrovejo updated GORA-326:
---------------------------------------------------
Attachment: GORA-326.v1.patch
This patch solves the issue by making the __g__dirty field part of the
PersistentBase class. As this field is only used by Gora it doesn't make sense
to put it in all user's data beans. I have updated the datastores affected by
this, but the gora-compiler will need a bigger cleanup as the dirty support
won't be made from the schemas but from Gora itself.
> Removal of _g_dirty field from _ALL_FIELDS array and Field Enum in Persistent
> classes
> -------------------------------------------------------------------------------------
>
> Key: GORA-326
> URL: https://issues.apache.org/jira/browse/GORA-326
> Project: Apache Gora
> Issue Type: Improvement
> Components: gora-core
> Affects Versions: 0.4
> Reporter: Alparslan Avcı
> Priority: Minor
> Labels: gora-core
> Fix For: 0.5
>
> Attachments: GORA-326.patch, GORA-326.v1.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
