[Doctrine] #1394: MySQL Spatial extension support

[Doctrine]

#1394: MySQL Spatial extension support
-----------------------------------+----------------------------------------
Reporter: davehimself | Owner: jwage
Type: enhancement | Status: new
Priority: minor | Milestone: New
Component: Attributes | Version: 0.11
Keywords: | Has_test: 0
Mystatus: Pending Core Response | Has_patch: 1
-----------------------------------+----------------------------------------
Currently the Data Dict for MySQL does not support the spatial extensions.
generateModelsFromDb() will throw an exception and die when trying to
reflect a table with a spatial field. I'm attaching a diff which can be
applied to make the geometry type work. There are many other types which
need to be implemented for full gis/spatial support.

--
Ticket URL: <http://trac.doctrine-project.org/ticket/1394>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper

[Doctrine]

#1394: MySQL Spatial extension support

--------------------------+-------------------------------------------------
Reporter: davehimself | Owner: jwage
Type: enhancement | Status: closed

Priority: minor | Milestone: New
Component: Attributes | Version: 0.11

Resolution: fixed | Keywords:

Has_test: 0 | Mystatus: Pending Core Response
Has_patch: 1 |

--------------------------+-------------------------------------------------
Changes (by guilhermeblanco):

* status: new => closed
* resolution: => fixed

Comment:

(In [4858]) fixes #1394. Thanks for the patch!

--
Ticket URL: <http://trac.phpdoctrine.org/ticket/1394#comment:1>

[Doctrine]

#1394: MySQL Spatial extension support

--------------------------+-------------------------------------------------
Reporter: davehimself | Owner: jwage
Type: enhancement | Status: reopened

Priority: minor | Milestone: New
Component: Attributes | Version: 0.11

Resolution: | Keywords:

Has_test: 0 | Mystatus: Pending Core Response
Has_patch: 1 |

--------------------------+-------------------------------------------------
Changes (by romanb):

* status: closed => reopened
* resolution: fixed =>

Comment:

geometry is no portable type. this patch is wrong.

--
Ticket URL: <http://trac.doctrine-project.org/ticket/1394#comment:2>

[Doctrine]

#1394: MySQL Spatial extension support

--------------------------+-------------------------------------------------
Reporter: davehimself | Owner: jwage
Type: enhancement | Status: reopened

Priority: minor | Milestone: New
Component: Attributes | Version: 0.11

Resolution: | Keywords:

Has_test: 0 | Mystatus: Pending Core Response
Has_patch: 1 |

--------------------------+-------------------------------------------------
Comment (by davehimself):

I feel that to say the patch is wrong is a little harsh. Not supporting
this type is a show-stopper for me. I would hate to not be able to use
Doctrine on account of a "non-portable type". IMHO, if Doctrine will not
support "non-portable" types, then can the type abstraction be factored
into classes with an API to allow users to define their own types? I
looked for this functionality in the docs, but did not find it. I just
assumed that it was not available.

--
Ticket URL: <http://trac.doctrine-project.org/ticket/1394#comment:3>

[Doctrine]

#1394: MySQL Spatial extension support

--------------------------+-------------------------------------------------
Reporter: davehimself | Owner: jwage
Type: enhancement | Status: reopened

Priority: minor | Milestone: New
Component: Attributes | Version: 0.11

Resolution: | Keywords:

Has_test: 0 | Mystatus: Pending Core Response
Has_patch: 1 |

--------------------------+-------------------------------------------------
Comment (by romanb):

Replying to [comment:3 davehimself]:

> I feel that to say the patch is wrong is a little harsh. Not supporting
this type is a show-stopper for me. I would hate to not be able to use
Doctrine on account of a "non-portable type". IMHO, if Doctrine will not
support "non-portable" types, then can the type abstraction be factored
into classes with an API to allow users to define their own types? I
looked for this functionality in the docs, but did not find it. I just
assumed that it was not available.

We are going to do sth like that in 2.0 (API for types and custom types).
I am not sure at the moment how to deal with this in earlier versions like
1.0. Maybe we should open up the gates and just allow any kinds of column
types, leaving the portability choice entirely to the user? We ended up
doing this for functions in DQL, too, maybe we should do this here, too.

--
Ticket URL: <http://trac.phpdoctrine.org/ticket/1394#comment:4>

[Doctrine]

#1394: MySQL Spatial extension support

--------------------------+-------------------------------------------------
Reporter: davehimself | Owner: jwage
Type: enhancement | Status: reopened

Priority: minor | Milestone: New
Component: Attributes | Version: 0.11

Resolution: | Keywords:

Has_test: 0 | Mystatus: Pending Core Response
Has_patch: 1 |

--------------------------+-------------------------------------------------
Comment (by romanb):

Also, importing should already work (in the 1.0 branch). Theres nothing
against importing a native type into a portable type (like blob).

--
Ticket URL: <http://trac.phpdoctrine.org/ticket/1394#comment:5>

[Doctrine]

#1394: MySQL Spatial extension support

--------------------------+-------------------------------------------------
Reporter: davehimself | Owner: jwage
Type: enhancement | Status: reopened
Priority: minor | Milestone: 1.1.0
Component: Attributes | Version:
Resolution: | Keywords:

Has_test: 0 | Mystatus: Pending Core Response
Has_patch: 1 |

--------------------------+-------------------------------------------------
Changes (by jwage):

* version: 0.11.0 =>
* milestone: => 1.1.0

--
Ticket URL: <http://trac.doctrine-project.org/ticket/1394#comment:7>

[Doctrine]

#1394: MySQL Spatial extension support

--------------------------+-------------------------------------------------
Reporter: davehimself | Owner: jwage
Type: enhancement | Status: closed

Priority: minor | Milestone: 1.1.0
Component: Attributes | Version:

Resolution: fixed | Keywords:

Has_test: 0 | Mystatus: Pending Core Response
Has_patch: 1 |

--------------------------+-------------------------------------------------
Changes (by jwage):

* status: reopened => closed
* resolution: => fixed

Comment:

In r5232 this was fixed again. The last patch was not quite correct.

--
Ticket URL: <http://trac.doctrine-project.org/ticket/1394#comment:8>