Some providers such as SQL Server do not use WKT for describing spatial context coordinate systems. As coordinate system transformations are driven by source/target WKTs, if either source or target does not have a WKT, we need to be able to infer one from an alternate data point such as the coordinate system name. Basically, do what MapGuide does and fill in the WKT from the coordsys catalog assuming the cs name corresponds to the mentor CS code.
On a similar vein, this realization means that need the ability to also specify an override CS name as the override WKT doesn't really have much useful effect for SQL Server.
Some providers such as SQL Server do not use WKT for describing spatial context coordinate systems. As coordinate system transformations are driven by source/target WKTs, if either source or target does not have a WKT, we need to be able to infer one from an alternate data point such as the coordinate system name. Basically, do what MapGuide does and fill in the WKT from the coordsys catalog assuming the cs name corresponds to the mentor CS code.
On a similar vein, this realization means that need the ability to also specify an override CS name as the override WKT doesn't really have much useful effect for SQL Server.