Description:
When inserting geometry data using the well known text methods, the data is inserted properly. However, if providing the same data via the well known binary methods, the srid information is not included in the blob even though it was included in the function's second optional parameter.
This can be demonstrated with the following query:
SELECT hex(PointFromWKB(Point(0, 0), 4326)), hex(PointFromText('Point(0 0)', 4326));
This query, on the mysql versions tested, yielded the following results:
hex(PointFromWKB(Point(0, 0), 4326)): 00000000010100000000000000000000000000000000000000
hex(PointFromText('Point(0 0)', 4326)):
E6100000010100000000000000000000000000000000000000
Although the srid is being provided in both functions, it is only included in the blob with the 'FromText' functions (the same issue occurs when using the more generic GeomFromText/WKB functions). This is a signifigant annoyance, especially if trying to utilize a unique constraint, as the two points should be equivalent, but is not because the underlieing method of insert was different.
How to repeat:
Execute the following query:
SELECT hex(PointFromWKB(Point(0, 0), 4326)), hex(PointFromText('Point(0 0)', 4326));
Notice that the first value is lacking the E610 prefix that is found in the second value.
Suggested fix:
PointFromWKB should include the srid in the blob if provided. The two values from the previous query should be identical.
Description: When inserting geometry data using the well known text methods, the data is inserted properly. However, if providing the same data via the well known binary methods, the srid information is not included in the blob even though it was included in the function's second optional parameter. This can be demonstrated with the following query: SELECT hex(PointFromWKB(Point(0, 0), 4326)), hex(PointFromText('Point(0 0)', 4326)); This query, on the mysql versions tested, yielded the following results: hex(PointFromWKB(Point(0, 0), 4326)): 00000000010100000000000000000000000000000000000000 hex(PointFromText('Point(0 0)', 4326)): E6100000010100000000000000000000000000000000000000 Although the srid is being provided in both functions, it is only included in the blob with the 'FromText' functions (the same issue occurs when using the more generic GeomFromText/WKB functions). This is a signifigant annoyance, especially if trying to utilize a unique constraint, as the two points should be equivalent, but is not because the underlieing method of insert was different. How to repeat: Execute the following query: SELECT hex(PointFromWKB(Point(0, 0), 4326)), hex(PointFromText('Point(0 0)', 4326)); Notice that the first value is lacking the E610 prefix that is found in the second value. Suggested fix: PointFromWKB should include the srid in the blob if provided. The two values from the previous query should be identical.