Doctrine\ORM\Query\AST\Functions\FunctionNode::parse() has a @return void annotation, which might become a native return type declaration in the future.

Symfony's DebugClassLoader checks for inconsistencies between return types in classes and their parents/interfaces, and triggers a deprecation notice every time the library is used in a Symfony dev environment. This @return annotation fixes that.

I think I found a very confusing bug which is easy to replicate:

Test script

$lat = 52.092876;
$lon = 5.104480;
var_dump($lat, $lon);
$point = new \LongitudeOne\Spatial\PHP\Types\Geometry\Point($lat, $lon);
var_dump($point->getLatitude(), $point->getLongitude());

Outputs

float(52.092876)
float(5.10448)
float(5.10448)
float(52.092876)

https://github.com/longitude-one/doctrine-spatial/blob/main/lib/LongitudeOne/Spatial/PHP/Types/AbstractPoint.php#L202 Refers as Lat Lon construct (in this order) and writes lat to X and lon to Y

This is the issue: When using getLatitude() it will return the data from Y instead of X. https://github.com/longitude-one/doctrine-spatial/blob/main/lib/LongitudeOne/Spatial/PHP/Types/AbstractPoint.php#L65

Would changing the getLatitude and getLongitude fix it entirely or is there unintended side effects for this?

Because of doctrine updates, there are still some deprecated functions.

OrmMockTestCase.php:

• setMethods *2
• setMetaDataCacheImpl (fixed by #6)

OrmTestCase.php:

• executeUpdate
• exec
• setMetaDataCacheImpl (fixed by #6)

WrappingTest.php:

• class Doctrine\DBAL\Version is deprecated

An error appears when starting test jobs after the PR #4 was submitted.

This error isn't due to the PR.

3. LongitudeOne\Spatial\Tests\DBAL\Types\Geography\GeoPolygonTypeTest::testNullPolygon Error: Class 'Doctrine\Common\Cache\ArrayCache' not found

Replace all ORMException

namespace Doctrine\ORM;

/**
 * Base exception class for all ORM exceptions.
 *
 * @deprecated Use Doctrine\ORM\Exception\ORMException for catch and instanceof
 */
class ORMException extends Exception

For additional security you should declare the allow-plugins config with a list of packages names that are allowed to run code. See https://getcomposer.org/allow-plugins You have until July 2022 to add the setting. Composer will then switch the default behavior to disallow all plugins.

Message : You are running PHP CS Fixer v2, which is not maintained anymore. Please update to v3. You may find an UPGRADE guide at https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/v3.3.0/UPGRADE-v3.md

Some tests now failed because of doctrine updates. This is due to :

• updates on namespaces
• final classes cannot be mocked
• some Postgresql functions returns values in another order

Fixtures for functional tests should be internal to avoid that PHPStorm or any other code editor purpose these non-useful classes during autocompletion.

Replacing no-more existing Doctrine\Common\Cache\ArrayCache by Cache\Adapter\PHPArray\ArrayCachePool Replacing deprecated method setMetadataCacheImpl from Doctrine\ORM\Configuration by setMetadataCache

Hi there.

First thing first: thank you for this package.

Let's talk about the following example:

CREATE TABLE `table_foobar` (
  `name` varchar(19) NOT NULL,
  `position` point DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_unicode_ci;

$point = new Point($longitude, $latitude);

$connection->insert(
  'table_foobar',
  [
    'name' => 'john',
    'position' => new Point(2.35222, 48.8566);
  ],
 [
    'position' => new PointType(),
  ]
);

I get the following exception.

[Doctrine\DBAL\Exception\DriverException]
  An exception occurred while executing 'INSERT INTO `table_foobar` (name, position) VALUES (?, ?)' with params ["john", "POINT(2.35222 48.8566)"]:

  SQLSTATE[22003]: Numeric value out of range: 1416 Cannot get geometry object from data you send to the GEOMETRY field

Do you have any clue to solve this error?

Note that I'm just using DBAL Doctrine integration.

Regards.

Mysql 8 can save PONT like this: ST_SRID(POINT(...), 4326) But

            $point = new Point($lon, $lat);
            $point->setSrid(4326); # !!!!!!!!!!
            $entity->setPoint($point);

Not working - SRID did not saved

Is there a way to go around the SQLite limitation? I use it only for fast testing and tests don't even need to cover this value.

The error I get when I try to update schema:

In AbstractSpatialType.php line 235:
                                                      
DBAL platform "sqlite" is not currently supported. 

The only idea I have is to make a Doctrine event that would completely remove it when in test environment but that sounds very wrong.

There is no test for the next files:

• PostGis: SpScale.php
• PostGis: SpTransform.php
• PostGis: SpTranslate.php
• Standard: StConvexHull.php(https://coveralls.io/builds/40810010/source?filename=lib%2FLongitudeOne%2FSpatial%2FORM%2FQuery%2FAST%2FFunctions%2FStandard%2FStConvexHull.php)