So I've started using HeidiSQL to access our MSSQL (SQL Server) database at work, as I find it a lot lighter and more intuitive than the Microsoft tool.
However, I noticed the data type hierarchyid is not handled correctly. Some weird asian characters are displayed instead of the actual /1/2/ or whatever value.
Is there any plan to fix this?
Thanks!
MSSQL - handling "hierarchyid" data type?
https://msdn.microsoft.com/en-us/library/bb677290.aspx
It's a bit special... basically it's an hexadecimal number but can be displayed like /1/, /1/1/, /1/2/, /2/1/, etc. In SQL Server you can use ToString() to view this representation, which is the most human-readable.
It's a bit special... basically it's an hexadecimal number but can be displayed like /1/, /1/1/, /1/2/, /2/1/, etc. In SQL Server you can use ToString() to view this representation, which is the most human-readable.
Code modification/commit
from ansgar.becker,
9 years ago,
revision 9.1.0.4900
Add support for MSSQL data type HIERARCHYID. See http://www.heidisql.com/forum.php?t=17575
Done in r4900. Such columns should be detected now as HIERARCHYID in the table editor. The date type group is "Other", just like "CURSOR", "SQL_VARIANT" and some others.
The conversion with TOSTRING() did not work here. ("ToString is not detected as an internal function"). So I followed the documentation which says that CAST(x AS NVARCHAR(y)) does the same, implicitly.
Please update to the latest build and test.
The conversion with TOSTRING() did not work here. ("ToString is not detected as an internal function"). So I followed the documentation which says that CAST(x AS NVARCHAR(y)) does the same, implicitly.
Please update to the latest build and test.
Please login to leave a reply, or register at first.