in our application we want to use doctrine2, however there is one function that we want to offer, but I am completely confused about how it will work.
we want our customers to be able to define custom fields for our standard objects. therefore, these fields will be executed on the fly, and not part of the definition of an object that is known and displayed by the doctrine.
our first thought was to use nosql (mongodb or amazon dynamodb) to store some of this data, but since we want to use the doctrine to process our core objects, we would like to stay within the doctrine to achieve this without having to go beyond it limits to save this data.
one thing, in my opinion, used the ability of the doctrine to serialize / unserialize complex objects and simply have a hash of custom field names and their values as an additional property in the object, however this will not allow us to have a function that will look for these fields if we ever either want it ...
Has anyone tried to do this with doctrine2 or any orm variant?
source
share