#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 <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"doctrine-svn" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.co.uk/group/doctrine-svn?hl=en-GB
-~----------~----~----~----~------~----~------~--~---
