Problem with Non-nullable nvarchar columns

Topics: User Forum
Mar 16, 2007 at 6:59 PM
We are having trouble with a database table that contains non-nullable nvarchar columns. When you try to load data with the InsertManager, an exception is thrown in TableBase.CreateTableObjectFromDatabase.

What seems to be happening is:
  • The routine is trying to load all of the required fields into a dictionary
  • The SQL query to find the columns returns duplicate rows because nvarchar and sysname have the same "systemtypeid"
  • The routine tries to add the column to the StringDictionary twice, which throws an exception

Is there any possibility that this will get fixed? Could I submit a patch?