tag:blogger.com,1999:blog-8791723.post110493829948880471..comments2023-09-22T11:01:30.370-07:00Comments on Val the C# Gal: One to One RelationshipsValerie Vogthttp://www.blogger.com/profile/14342788492213089415noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-8791723.post-1129943215183070792005-10-21T18:06:00.000-07:002005-10-21T18:06:00.000-07:00Hi,I was just looking around the net for web sites...Hi,<BR/><BR/>I was just looking around the net for web sites related to love relationship test and came across your blog. I was going to add a blog to my site, for <A HREF="http://www.love-blog.info" REL="nofollow">love relationship test</A> and of course other related material, but I'm not sure if it would work.<BR/>I'm a bit worried about getting un-wanted 'rude' posts rather than ones related to <A HREF="http://www.love-blog.info" REL="nofollow">love relationship test</A> on my site...... perhaps I just try it out - then you can come and post on it :)<BR/><BR/>Take care<BR/>StewartAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8791723.post-1105062723709932572005-01-06T17:52:00.000-08:002005-01-06T17:52:00.000-08:00I personally prefer to have the ID of the parent t...I personally prefer to have the ID of the parent table in each of the children. Because you haven't duplicated all the information into the child tables, this allows you quick search access to all the information from which you can drill down to get at a lower level of detail.<br /><br />With regards to XML, I currently don't like this approach. Like Andy said, querying isn't very good. This could change with Sql2k5's introduction of an actual XML column type that can be queried...but I'm still not sold that it is the best way to go.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8791723.post-1104960731245857612005-01-05T13:32:00.000-08:002005-01-05T13:32:00.000-08:00Andy-
Cool idea. I have not heard of that soluti...Andy-<br /><br />Cool idea. I have not heard of that solution before. So you have to use an stream reader to get the data out of the XML file, which is fine because your domain layer can do that work for you. Have you used this approach before? Were there any reporting implications?<br /><br />Thanks-<br />ValerieValerie Vogthttps://www.blogger.com/profile/14342788492213089415noreply@blogger.comtag:blogger.com,1999:blog-8791723.post-1104954669941824872005-01-05T11:51:00.000-08:002005-01-05T11:51:00.000-08:00Andy-
You are right. I should have said "In the ...Andy-<br /><br />You are right. I should have said "In the Owner table, Employee table, and Contact table, the IndividualID would also be a foreign key to the Individual table."<br /><br />I do agree that you could get around this whole issue by either including the Indivudal columns in each of the Owner, Employee, and Contact tables and getting rid of the Indivudual table. That solution just doesn't sit right with me because of the duplication of information. So in that scenario, if an Invidual has a new attribute, you have to add the column to three tables instead of one.<br /><br />I also agree that a solution is to move all of the columns from the Owner, Employee, and Contact table into the Individual table, and only use the columns that apply. I know that database storage space is not really an issue any longer, and maybe it just a throwback from those days, but when I see a bunch of columns that should be null in 1/3 of the cases, I hate including them in the table.<br /><br />I do have my domain objects and mappers set up to support the "is a" relationship, I was just wondering if there is a commonly accepted practice that I do not know about.<br /><br />Thanks for your feedback-<br />ValValerie Vogthttps://www.blogger.com/profile/14342788492213089415noreply@blogger.comtag:blogger.com,1999:blog-8791723.post-1104943831037330822005-01-05T08:50:00.000-08:002005-01-05T08:50:00.000-08:00I prefer the first option, IndividualID in all 4 t...I prefer the first option, IndividualID in all 4 tables.<br /><br />1) less columns<br />2) more logical since Individual is the supertypeHassan Voyeauhttps://www.blogger.com/profile/04949411535244712466noreply@blogger.comtag:blogger.com,1999:blog-8791723.post-1104939840260403892005-01-05T07:44:00.000-08:002005-01-05T07:44:00.000-08:00JavaKid-
Are you suggesting we stop using Microso...JavaKid-<br /><br />Are you suggesting we stop using Microsoft tools? Or are you suggesting we build our own object-oriented database? I work in a consulting company who is a Microsoft Gold Partner, and since we specialize in Microsoft tools, I agree that I may tend to get stuck on the idea that I will deliver my enterprise solutions on the Microsoft platform.<br /><br />Do you know of any good object-oriented databases that you would recommend for enterprise solutions that use Microsoft's .Net platform? I would be very interested in hearing more.<br /><br />--Val the C# GalValerie Vogthttps://www.blogger.com/profile/14342788492213089415noreply@blogger.com