A much needed SchemaHelper class

My blog has moved.
You can view this post at the following address:
http://www.osherove.com/blog/2003/7/3/a-much-needed-schemahelper-class.html
Published Thursday, July 03, 2003 5:12 PM by RoyOsherove
Filed under:

Comments

Thursday, July 03, 2003 1:12 PM by TrackBack

# ISerializable

ISerializable
Saturday, January 31, 2004 10:40 AM by sotto

# re: A much needed SchemaHelper class

You write that this functionality does exist for sqlconnection ...
could you provide an example?
What i want to achieve is to get a dataset that holds the complete database in memory.
Tuesday, April 13, 2004 5:47 AM by Ido Samuelson

# re: A much needed SchemaHelper class

You could of let the helper get a connection thus having it support any kind of db

Great idea!

It fits great to my dbHelper that auto-generage insert,update,delete statments.

Wednesday, May 26, 2004 8:43 AM by Mahavir

# re: A much needed SchemaHelper class

I have run the exact thing, But I am getting a Blank Page, wonder whats wrong !
Wednesday, October 04, 2006 1:33 PM by eperales

# Inverted parameters

Thanks for this great helper. I think when you actually add a relation in CreateDataRelation the parameters ara inverted and should read ds.Relations.Add(RelationName,PKDataCol,FKDataCol); cheers!
Wednesday, October 25, 2006 4:54 AM by SqlClient

# re: A much needed SchemaHelper class

Well, it's all nice and easy for the OleDB provider, but the Sql Server support it's just useless. In order to build the relations within the dataset you still have to querry the database metadata instead of using the SqlConnection.
Wednesday, October 25, 2006 6:06 AM by Multiple columns involved

# re: A much needed SchemaHelper class

The SqlHelper class should be modified in order to include multiple column foreign keys