http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Epraim, Yes, it does. http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment18http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment18Wed, 30 Mar 2011 08:31:30 GMTHow are the newcolumns created in customer_extensions.Is it Nhibernate doing update schema on the database. http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment17http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment17Wed, 30 Mar 2011 07:09:11 GMTThis is great for basic types.But can I add a many to one relation problematically. http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment16http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment16Mon, 21 Mar 2011 13:16:07 GMTIs there any way to combine this with NHibernate Lucene Full text search? http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment15http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment15Thu, 17 Mar 2011 10:07:41 GMTJanis, I was actually referring to: > In general, I would recommend anyone that needs dynamic fields to work with a data storage solution that supports it (like RavenDB , for example). But in response to your other questions: - You can put a collection in a dynamic property. - You can edit the configuration programatically http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment14http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment14Sat, 12 Mar 2011 16:35:42 GMTuuu..? you still using a xml mapper and need to edited the xml file for adding new fields... i don't see that you are getting a collection from the database.. <property has only one propertie.. it isn't a collection.. so if i need to add Eyesize i need to put <property in it :s.... oke.. you don't need to add it in the .net code.. but you have to edit in backend the xml file.. :S.. >http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment13http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment13Sat, 12 Mar 2011 09:40:53 GMTJanis, I guess you missed the part where I recommended doing just that, then... http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment12http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment12Sat, 12 Mar 2011 08:46:24 GMTlooks nice.. but i don't like it that you need to write in the xml file properties of a dynamic field.. why... because it isn't dynamic any more.. if there is a new field you have to go in the code to add it.. that's why this is better to use it with mongodb because of the json solution. you don't need to use xml..or get in the code for adding a new field add field detail page on asp.net and it add this field in the document at the monogdb.. you can even search these dynamic fields.. that's the real dynamic.. gr. http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment11http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment11Fri, 11 Mar 2011 22:42:25 GMT@Frank: Whether different databases and schemas for different tenants are a good choice depends on the kind of software. Let's say you have a SaaS - based CRM-application and you want your customers to choose which fields make up a single business-contact. You need to find a way, to dynamically allow to customize the contact-entity. In such a case it would not only be a waste of memory (each db-instance can take up to hundreds of mb) but also a unnecessary overhead while managing updates, backups, etc. @Oren: Would you say that RavenDB would be a good choice in such a situation? http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment10http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment10Wed, 09 Mar 2011 13:30:58 GMTHazzik, Since the data storage in a RDBMS, you really have no choice. Daniel, You should use different schemas / databases for different tenants. http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment9http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment9Wed, 09 Mar 2011 12:55:37 GMTDaniel, I guess supporting different customers with different schemas on the same DB schema will always be an interesting proposition. http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment8http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment8Wed, 09 Mar 2011 10:06:49 GMTGreat stuff, in v3.0 NHibernate has really outgrown the "ORM" moniker and is on its way to becoming a platform. @hazzik: I believe you could use ConfORM or Fluent NHibernate to do the mapping dynamically. http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment7http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment7Wed, 09 Mar 2011 09:58:44 GMTI think the main advantage of this approach is the huge performance benefit over an EAV model. Unfortunately I don't see a way to get this working in a multi-tenant architecture, where different tenants need to have individual fields, while still using on the same DB. http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment6http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment6Wed, 09 Mar 2011 06:39:24 GMTSo, I need to define each of dynamic field in the mapping? I think it is ugly. http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment5http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment5Wed, 09 Mar 2011 06:14:37 GMTNice post. Jeremy Miller has posted some good blog posts on the same topic. [codebetter.com/.../our-extension-properties-story/](http://codebetter.com/jeremymiller/2010/02/16/our-extension-properties-story/) [codebetter.com/.../how-do-you-extend-and-custom...](http://codebetter.com/jeremymiller/2007/02/19/how-do-you-extend-and-customize-a-database/)http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment4http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment4Tue, 08 Mar 2011 23:23:24 GMTI would say using some kind of IUserType (I do not remember if <dynamic-component allows that) to create the HashtableDynamicObject would be better. Otherwise anyone who refactors the code to virtual dynamic Attributes { get; private set; } will break it, because it is not obvious that this field is used externally. >http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment3http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment3Tue, 08 Mar 2011 21:14:18 GMTYeah, thats really cool and easy. And btw it is good to read some interesting stuff again after a long time... :-) http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment2http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment2Tue, 08 Mar 2011 21:13:13 GMTVery nice indeed! http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment1http://ayende.com/4776/support-dynamic-fields-with-nhibernate-and-net-4-0#comment1Tue, 08 Mar 2011 18:22:10 GMT