Unable to save/load large geometries using MsSql dialect

[peetw]

Anyone else having issues saving large polygon geometries?

Originally posted by @mikemcdougall in #84 (comment)

[peetw]

@mikemcdougall what issues are you having exactly? Do you have a test case you can share?

Originally posted by @peetw in #84 (comment)

[peetw]

@peetw
I found the issue I was having with large geometries.
The problem is in MsSqlGeometryType.cs in the Set(DbCommand cmd, object value, int index, ISessionImplementor session) function.
I changed to
parameter.SqlDbType = SqlDbType.VarBinary;
parameter.Size = ((byte[]) value).Length;

the SqlDBType.Binary has a max of 8000 bytes. So the value being passed in the parameter was being cut off. Sql server was sending back invalid geometry error. Seems to be working with the above changes.

Would you like me to create PR?

Originally posted by @mikemcdougall in #84 (comment)

[peetw]

@mikemcdougall Great, nice work! I'll try and take a look at the PR ASAP.

Originally posted by @peetw in #84 (comment)

[peetw]

@mikemcdougall Your fix has now been merged in and is included in a new v5.3.0 release, which is now available on NuGet 🎉