Main

TMCore07 Archives

August 21, 2009

Known Issue: TMCore07 SP4 - Display of non-ascii characters

Description

TMCore07 SP4 included a fix for the tm_displayName function in the TMCore database that provides the default display name for a topic. Prior to SP4, this function returned a varchar result which meant that non-ASCII characters would display as a ?. From SP4 the function was updated to return an nvarchar result, allowing any Unicode characters to be correctly displayed. Unfortunately the early release of the SP4 package did not include this updated function in the database upgrade script.

Systems Affected
This problem will show up only on databases that have been upgraded from a previous version of TMCore - clean database installations are not affected by this problem. In addition, the TMCore07 SP4 installer has been fixed so that downloads of the installer taken on or after the 21st August 2009 do not exhibit this problem either for new databases or for upgraded databases.

Fix

If you downloaded TMCore07 SP4 prior to 21st August 2009, you can apply the update for the tm_displayName function by running the following SQL script against the TMCore database:

-------------------------------------------------------------------
-- tm_displayName
-- Returns a display string for a topic selected from the topics variant names and topic names.
-- Since: 1.0
-- Last Updated: 2.4
if exists (select * from sysobjects
where id = object_id(N'[tm_displayName]') and
xtype in(N'FN',N'IF',N'TF'))
DROP FUNCTION [tm_displayName]
go
CREATE FUNCTION dbo.tm_displayName (@topic int)
RETURNS nvarchar(512)  AS
BEGIN
DECLARE @disp int
DECLARE @ret nvarchar(512)
SELECT @disp = (SELECT TOP 1 topic_id from tm_si
WHERE
tm_si.topicmap = (select topicmapref from topic where id = @topic) and
subj_id='http://www.topicmaps.org/xtm/1.0/core.xtm#display')
SET @ret = (SELECT TOP 1 variant_value FROM tm_nameVariantValue JOIN tm_variantScope ON tm_nameVariantValue.variant_id = tm_variantScope.variant_id
WHERE
tm_nameVariantValue.topic_id = @topic AND tm_variantScope.scoping_topic_id = @disp
ORDER BY tm_nameVariantValue.variant_id ASC)
IF (@ret IS NULL)
SET @ret = (SELECT TOP 1 name_value FROM tm_nameValue JOIN tm_nameScope ON tm_nameValue.name_id = tm_nameScope.name_id
WHERE
tm_nameValue.topic_id = @topic AND tm_nameScope.scoping_topic_id = @disp
ORDER BY tm_nameValue.name_id ASC)
IF (@ret IS NULL)
SET @ret = (SELECT TOP 1 name_value FROM tm_nameValue JOIN tm_nameScope ON tm_nameValue.name_id = tm_nameScope.name_id
WHERE
tm_nameValue.topic_id = @topic and ((tm_nameScope.scoping_topic_id IS NULL)  or (tm_nameScope.scoping_topic_id = -1))
ORDER BY tm_nameVALUE.name_id ASC)
IF (@ret IS NULL)
SET @ret = (SELECT TOP 1 name_value FROM tm_nameValue WHERE tm_nameValue.topic_id = @topic ORDER BY tm_nameValue.name_id)
RETURN @ret
END
GO
grant exec on tm_displayName to tm_reader, tm_writer
go

July 31, 2009

TMCore07 SP4 Released

NetworkedPlanet today announces the release of latest version of the TMCore topic map engine. TMCore is the premiere toolkit for developers on .NET looking to harness the full power of Topic Maps in their applications. Built from the ground-up using .NET technologies, TMCore provides a flexible set of APIs and builds on the robustness, scalability, performance of Microsoft's SQL Server.

The new SP4 release of TMCore07 provides a number of bug fixes and performance enhancements and is a recommended upgrade for all customers. Customers having a current support contract receive TMCore07 SP4 free of charge. For download details please email us at contact@networkedplanet.com.

The following fixes and updates have been made in this release:

BUGFIX: TMEditor now properly displays non-latin characters in browsers that have support for rendering them correctly.
PERFORMANCE: Performance of the stored procedures for duplicate suppression has been greatly increased while also decreasing the amount of server memory required to complete the duplicate removal process on large topic maps.
BUGFIX: TMEditor now supports editing association role constraints for reflexive associations
BUGFIX: The NPCL import process now allows importing duplicate association role constraints on an association. This fix enables users to define reflexive associations using multiple association role constraints with the same role type.
BUGFIX: The tm_npcl* views have been fixed to eliminate duplicate entries and improve performance.
BUGFIX: tmimport.exe and tmexport.exe now return a non-zero status code when an error is encountered.
BUGFIX: XTM export has been fixed to not export associations with no roles in order to avoid generating invalid XTM output.
BUGFIX: The NPCL Forms export has been fixed to avoid generating invalid output when the NPCL schema contains inconsistencies.

December 3, 2007

TMCore07 SP3 Known Issues, Fixes and Workarounds

TMCore07 SP3 Known Issues, Fixes and Workarounds

This blog entry is used to record and document known issues found with TMCore07 SP3 edition and their current status.

If you discover an issue with TMCore07 SP3 that is not listed here, then please report it to us at support@networkedplanet.com.

Ref.IssueResolution
634, 635, 636 The web.config files supplied with TMService, NPCL-WS and TMEditor declare a log4net configuration section named NetworkedPlanet.<application name>.log4net. Log4net requires that the configuration section is named log4net therefore any log4net configuration information specified using the existing names will be ignored. The TMCore07 SP3 installer has been updated (on 3rd December 2007) to fix this issue. For installations created with an installer downloaded prior to this date, this issue can be manually fixed simply by renaming the section in the web.config files.

About TMCore07

This page contains an archive of all entries posted to NetworkedPlanet On Topic in the TMCore07 category. They are listed from newest to oldest.

Many more can be found on the main index page or by looking through the archives.

Subscribe to this blog's feed