Working with legacy databases in NHibernate Part 1 - Compound foreign keys

Revisions

Compare	Revision	Minor	Date	Status	Editor
	4	No	27 Nov '12 - 4:05	Pending	Pete Sutcliffe
Error in Equals code
	3	No	27 Nov '12 - 3:55	Pending	Pete Sutcliffe
Small fix to error
	2	No	23 Nov '12 - 13:06	Available	Sean Ewington
Updates in content.
	1	No	22 Nov '12 - 13:11	Draft	Pete Sutcliffe

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

About the Author

Pete Sutcliffe

Software Developer (Senior) AJ Systems

United Kingdom

Member

I am currently a developer at a management consultancy company.
In addition to all things .NET I have a keen interest in Japan and the Japanese language and hope to be able to combine these passions one day soon.

A Technical Blog, originally posted at http://www.pdsutcliffe.co.uk/Blog/post/2012/11/12/Working-with-legacy-databases-in-NHibernate-Part-1-Compound-keys.aspx

If there's anything worse than working with legacy code, it's working with Legacy databases. At least with legacy code if you're lucky you can ring-fence it off and ignore it when not working on it, but poorly designed databases can infect a whole system and create a situation where your new code st

Type	Technical Blog
Licence	CPOL
First Posted	23 Nov 2012
Views	2,516
Bookmarked	3 times

NHibernate

		9,889,766 members (39,409 online) Visit CodeProject.TV Discuss CodeProject.TV Sign in Email Password Forgot your password? Sign in using