It's implemented as a struct when possibly a class would be more appropriate.
This isn't really an issue in practice as it appears to be used very infrequently: #70 (comment)
Because it's not used much, there's little backwards compatibility concern with changing its API. We should introduce a type that's suitable for use with spatial querying layers and that serves to mark a parameter value or returned result as unambiguously being a GEOMETRY value, not any arbitrary byte.
MySqlDataReader.GetValue should still return byte for GEOMETRY columns, but MySqlDataReader.GetMySqlGeometry and GetFieldValue<MySqlGeometry> should be implemented.
The text was updated successfully, but these errors were encountered: