Is it possible to create a content in orchard core with 1 to n relation? For example create a content which register a person with several addresses!
Thanks in advance
Í solved it with bag. I created bag for each entity that needed to be a list
Related
In my KeystoneJS (v4) setup I have the following lists:
Stores
Product Categories
Tags
The stores can have categories associated with them.
If I open up a category I can see it's Relationships (stores that use a certain category).
But, is it possible to see these relationships in the list layout as well? Not seeing it in the docs...
Adding the relationship to the column is not possible.
My app has pre-populate Category data contain icon image and its name. In the next version I need to localized its name, is this possible ? Found Adding relation for localized methods here, but this is an only way to do it ?
There is no "Localize" feature build in to Core Data. So adding the localized names in a separate entity as mentioned in How to represent a localized string type in Core Data? is the way to go.
Is it possible to create some kind of one to many relationship between two lists into Microsoft SharePoint 2010? If it's possible i'd like to know how.
Let me know,
Thanks.
It depends on exactly what you want. You can create a lookup to another list using the custom fields within a list or content type.
But if you want to go to the maximum with one to many relationships then you would have to create a custom field using some custom field using c# code.
Can I prefix all the Liferay tables that it initially creates by doing some configuration changes.
I am new to Liferay and analyzing it for my use.
I gather that new tables being created are prefixed to avoid any conflicts but I have a situation where it suits me better if its other way round.
The answer is no for tables that Liferay creates on its first start. And as you have found yes for newly created tables using servicebuilder(uses the namespace tag)
In the book .NET Domain-Driven Design with C# from Tim McCarthy there's an example of a link table (two foreign keys + one boolean column) that gets it's own class in the domain. Is this common?
The example is a Contact table and a Project table. The link table is a ProjectContact. What are the pros and cons of using a class ProjectContact instead of having a List of Contacts property in the Project class and a List of Projects property in the Contact class?
I must say that having a ProjectContact class makes it easy to persist a new link between a Project and a Contact... but it seems overkill to me.
Pragmatically spoken (I'm not a DDD expert), I would say that a link table shouldn't pop up in the domain unless it is an entity on it's own (i.e. you need to attach behaviour to it, or it has properties other than the foreign keys).