Jira issue originally created by user jantichy:
In current custom mapping types implementation there is a limit that it maps one entity property to just one database column.
It would be great to be able to map one entity property do multiple database columns. It would make custom mapping types much more useful and elegant!
FOR EXAMPLE in my application I have a simple class for geo coordinates:
public function getLatitude() ...
public function getLongitude() ...
public function setLatitude($latitude) ...
public function setLongitude($latitude) ...
And I have an entity that besides all other properties has a point:
/*** @entity /
* @var Point
public function getPoint()
public function setPoint(Point $point)
$this->point = $point;
And database structure is something like this:
CREATE TABLE poi (
Advanced custom mapping types should be able to map my Point instance from entity property $point to both latitude and longitude columns in database and vice versa.
Yes, I can do it in some complicated way with @prePersist, @preUpdate... events, but use of custom mapping types is much more natural, elegant, transparent and reusable...
Is there a chance for rapid change of how custom mapping types act?
Comment created by @beberlei:
Duplicate of DDC-93
Issue was closed with resolution "Duplicate"
A related Github Pull-Request [GH-265] was