Samuel
Samuel

Reputation: 12341

Orchard CMS Database Part vs PartRecord

In Orchard database, there is tables name ending with 'Record' and other with 'PartRecord'.

What is the logic behind that?

Upvotes: 0

Views: 267

Answers (2)

Bertrand Le Roy
Bertrand Le Roy

Reputation: 17814

The tables for a part record should end in "PartRecord". If a table ends in "Record" without "Part" in front, it shouldn't map to a part record. For example, "ContentItemRecord" is a record, but not a part record. ContentItem is not a part.

Upvotes: 1

devqon
devqon

Reputation: 13997

Content part records are record classes that store content part data in the database.

While its not mandatory to have a part and a part record, it is a good practice to split the real data model (the record) from the model you are going to manipulate and/or read (the part).

The naming of the tables are all up to the module developers, but usually they are postfixed with PartRecord.

Looking at my Orchard database, I do not see any tables ending with Part. My guess is that with your application they are custom modules or third party modules, where the developer chose to postfix it with just Part.

Upvotes: 0

Related Questions