﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on Multi Table Entities in NHibernate</title><description>Mark, you can use DBLink to make the disparate database works, so yes.
  
For using Web Services, the answer is that technically, you may be able to do it.
  
Practically, it is not really a good solution, at least not in my opinion.
</description><link>http://ayende.com/2327/multi-table-entities-in-nhibernate#comment6</link><guid>http://ayende.com/2327/multi-table-entities-in-nhibernate#comment6</guid><pubDate>Thu, 03 May 2007 06:06:16 GMT</pubDate></item><item><title>Mark commented on Multi Table Entities in NHibernate</title><description>Is this something that can be done when the tables are in different databases?
  
  
A specific example might be that most of a salepersons information (address etc) is stored in an HR database however other information (general ledger code?) might be stored in a Financial systems database. Can these be brought together into one single entity.
  
  
To push the example even further, is there any way to make one of the sources a web service rather than a database table?
</description><link>http://ayende.com/2327/multi-table-entities-in-nhibernate#comment5</link><guid>http://ayende.com/2327/multi-table-entities-in-nhibernate#comment5</guid><pubDate>Thu, 03 May 2007 04:41:30 GMT</pubDate></item><item><title>Ayende Rahien commented on Multi Table Entities in NHibernate</title><description>Hm, the assoication in NHibernate for multi table entities is using a column in the sub-table that matches the PK of the entity.
  
  
I am not sure that I follow why this is a limitation, since I can't quite figure how you can have a single entity in multiply tables without assoication between them.
</description><link>http://ayende.com/2327/multi-table-entities-in-nhibernate#comment4</link><guid>http://ayende.com/2327/multi-table-entities-in-nhibernate#comment4</guid><pubDate>Wed, 02 May 2007 09:22:24 GMT</pubDate></item><item><title>Frans Bouma commented on Multi Table Entities in NHibernate</title><description>&gt;?? Can you explain? Do you mean the entity framework?
  
  
Yes. At the moment they can't update/insert/delete entities on multiple tables if they're not inheritance based or don't have the pk/fk fields inside them. WHich is logical, because that's also the reason why you can't update a view based on multiple tables in sqlserver/oracle etc.: they always update just 1 table.
</description><link>http://ayende.com/2327/multi-table-entities-in-nhibernate#comment3</link><guid>http://ayende.com/2327/multi-table-entities-in-nhibernate#comment3</guid><pubDate>Wed, 02 May 2007 07:50:45 GMT</pubDate></item><item><title>Ayende Rahien commented on Multi Table Entities in NHibernate</title><description>If you have a PK-FK assoication, I would say that this is another entity, and not the same one.
  
  
&gt; that's also the scope of the current EDM state
  
  
?? Can you explain? Do you mean the entity framework?
  
  
</description><link>http://ayende.com/2327/multi-table-entities-in-nhibernate#comment2</link><guid>http://ayende.com/2327/multi-table-entities-in-nhibernate#comment2</guid><pubDate>Wed, 25 Apr 2007 15:21:49 GMT</pubDate></item><item><title>Frans Bouma commented on Multi Table Entities in NHibernate</title><description>Still the scope is limited to PK-PK related tables. Nothing wrong with that, but that's also the scope of the current EDM state, as there's currently no way to insert fields in table B if the PK of B isn't in the entity at hand which is for example identified by the PK of table A, not related to B. 
</description><link>http://ayende.com/2327/multi-table-entities-in-nhibernate#comment1</link><guid>http://ayende.com/2327/multi-table-entities-in-nhibernate#comment1</guid><pubDate>Wed, 25 Apr 2007 15:12:53 GMT</pubDate></item></channel></rss>