MassDataHandler

Source code checked in, #99885

Project Collection Service Accounts — Mon, 01 Oct 2012 21:24:31 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #99884

Project Collection Service Accounts — Mon, 01 Oct 2012 21:16:08 GMT

Checked in by server upgrade

Source code checked in, #74794

_TFSSERVICE — Tue, 03 Aug 2010 19:44:57 GMT

Checked in by server upgrade

New Post: Heartbeat?

slickjuanito — Wed, 30 Dec 2009 18:57:10 GMT

Is this a dead project?

New Post: Heartbeat?

slickjuanito — Wed, 30 Dec 2009 18:57:10 GMT

Is this a dead project?

Reviewed: 1.3 Production (Jun 24, 2009)

pradeepneupane — Wed, 24 Jun 2009 10:01:31 GMT

Rated 4 Stars (out of 5) - nice application.wish u all d best

Source code checked in, #54243

timstall — Mon, 08 Jun 2009 16:53:03 GMT

Test1

Commented Issue: Problem with Non-nullable nvarchar columns

ondrejsv — Wed, 13 Aug 2008 07:05:24 GMT

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?
Comments: ** Comment from web user: ondrejsv **

Hello,

I came across this bug also but when I tried to get existing rows in a table with an nvarchar column. The exception being thrown was coming from the CreateTableObjectFromDatabase method and the framework was added the same value twice.

Fortunately, this bug is very easy to fix.

Open the DateUtilities.cs, find the GetColumnSchemaInfo method and change the SQL in the first line to this:

string strSql = @"
select
C1.Name as ""ColumnName"",
TP.name as ""SystemTypeName"",
C1.is_Nullable,
C1.max_length,
C1.is_Identity
from Sys.tables T1, Sys.columns C1, Sys.types TP
where
C1.object_Id = T1.object_id
and C1.user_type_id = TP.user_type_id
and T1.Name = '" + strTableName + @"'
order by C1.name
";

The only change is using user_type_id instead of system_type_id to join sys.columns and sys.types to get the type for a column. System_type_id is not a primary key of the sys.types view and beside nvarchar type there is one more row with the same id (sysname type), hence the loaded schema was incorrect.

NEW POST: Problem running quickstart

jhuygen — Fri, 15 Feb 2008 10:26:00 GMT

When I try to run the quickstart-application, I'm getting following exception:

Failed to queue test run 'xxx': Test Run deployment issue: The location of the file or directory 'c:\massdatahandler_1.3\massdatahandler\massdatahandler.tests\bin\debug\massdatahandler.tests.dll.config' is not trusted.

Do you have any idea what the problem could be?

NEW POST: QuickstartDemo.Tests.dll run fails.

ChrisWuestefeld — Thu, 19 Jul 2007 22:23:43 GMT

Yep, the annoying guy again... I've found that the build needs more tweaking to complete.

Again because of the 64-bit OS, my paths are different. Specifically in Database.sql I needed to change lines 14 and 16 to point the the (x86) version of Program Files.

After adjusting this, I'm still blocked when it tries to run the QuickstartDemo. I see the following:
C:\Projects\3rdParty\MassDataHandler_1.3\MassDataHandler\BuildProcess\RunTests.msbuild(52,5): error MSB3073: The command "MsTest "/testcontainer:C:\Projects\3rdParty\MassDataHandler_1.3\MassDataHandler\BuildProcess\..\QuickstartDemo.Tests\bin\Debug\QuickstartDemo.Tests.dll" "/resultsfile:C:\Projects\3rdParty\MassDataHandler_1.3\MassDataHandler\BuildProcess\..\BuildProcess\TestResults\QuickStartDemo.trx"" exited with code 1.

Looking at the .config file for QuickstartDemo.Tests.dll, it appears that the connection string's Data Source isn't set correctly (it doesn't match the value input to the form at the beginning). Fixing this, the tests all pass.

New Post: QuickstartDemo.Tests.dll run fails.

ChrisWuestefeld — Thu, 19 Jul 2007 22:23:43 GMT

NEW POST: MS Tools Directories

ChrisWuestefeld — Thu, 19 Jul 2007 21:55:49 GMT

Yes, definitely a stupid thing. I should have just tried it first. In my case the confusion was easily resolved. I'm running a 64-bit Windows, so the "Program Files" directory should have been "Program Files (x86)".

New Post: MS Tools Directories

ChrisWuestefeld — Thu, 19 Jul 2007 21:55:49 GMT

NEW POST: MS Tools Directories

ChrisWuestefeld — Thu, 19 Jul 2007 21:40:53 GMT

Perhaps I'm stupid. How would I know these directories? Are they the directories that certain tools are installed into (so I can tell by the presence of an .EXE) or are they the directories that those tools use for output or intermediate storage?

New Post: MS Tools Directories

ChrisWuestefeld — Thu, 19 Jul 2007 21:40:53 GMT

CREATED ISSUE: Problem with Non-nullable nvarchar columns

enicholson — Mon, 19 Mar 2007 15:34:19 GMT

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?

NEW POST: Problem with Non-nullable nvarchar columns

enicholson — Fri, 16 Mar 2007 18:59:20 GMT

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?

Thanks,
Eric

New Post: Problem with Non-nullable nvarchar columns

enicholson — Fri, 16 Mar 2007 18:59:20 GMT

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?

Thanks,
Eric

UPDATED WIKI: Home

timstall — Sat, 06 Jan 2007 04:39:09 GMT

The MassDataHandler is a framework to assist with Database Unit Testing. The framework makes it very easy to insert test data into a database, which in turn makes it very easy to write database unit tests. The user merely needs to specify their relevant data in a simple XML fragment, and then the framework uses knowledge of the database schema to do all the grunt work and convert that XML data into SQL, from which it populates the database.

The XML fragments that contain the test data are robust and refactorable. You can include expressions like variables substitution and identity lookup, default row templates, and include statements to import sub-templates. Because the framework already knows the database schema, you only need to specify the relevant data, and the framework can auto-populate the rest of the row’s required columns with dummy data.

This tool is intended for:

Supplying data for Database unit testing.
Easily creating your own data script to insert data for development.
Extracting data from one database and inserting it into another as test data.
Getting snapshots of data, and them converting them to xml files for easy diff comparisons.

The MassDataHandler framework was developed at Paylocity (http://www.paylocity.com) while working on our WebPay Payroll + HR system.

----

The MassDataHandler 1.3 has been released! (Jan 5, 2007)

It offers several new features:

Improved handling of identity values and triggers: (1) Triggers no longer break the identity inserts, (2) You can specify identity inserts for a table-by-table basis using an Xml attribute on the Table element, (3) If you set IdentityInsert=On for a table without Identity, then it no longer crashes.
Improved extracting from existing data: (1) The Existing Data tab can now use a custom select that returns many tables, and (2) When using Existing Data tab, if you use a Custom filter, it will copy your Sql select values into the Xml file as a meta node.
Some miscellaneous bug fixes and enhancements.

----

The MassDataHandler 1.2 has been released!

It offers several new features:

The GUI now offers the ability to ignore primary keys when generating from existing data.
The Build process has a reusable script to drop all foreign keys from a database. This makes it easier for you to adapt the demo script to your own project.
The Readme has been updated with better documentation.
A few miscellaneous bugs have been fixed.

CREATED RELEASE: 1.3 Production

Fri, 05 Jan 2007 08:00:00 GMT

Version 1.3