Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metadata #3

Closed
wants to merge 16 commits into from
Closed

Metadata #3

wants to merge 16 commits into from

Conversation

anpete
Copy link
Contributor

@anpete anpete commented Jan 29, 2014

This is a dummy PR for the EF team to review early metadata and basic infra work. NB: This will not be pushed to master :-)

@davidfowl
Copy link
Member

You mean dev

@anpete
Copy link
Contributor Author

anpete commented Jan 29, 2014

@davidfowl - RTFM! :-)

using JetBrains.Annotations;
using Microsoft.Data.Core.Utilities;

public class Entity : MetadataBase
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be EntityType; entities are instances of entity types.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure this distinction actually matters here:

  • This type is in Metadata.
  • Would we have another type called Entity representing an instance?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My initial thought was also EntityType, but I'm willing to try without the type for now and see how it ends up feeling.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One of my college professors always insisted on using the proper terminologies, so anything but entity type just feels wrong to me. I also got a little confused in the Model class at first thinking it was the change tracker (since it was adding entities and not entity types).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But the current fluent api also doesn't feel wrong since I read mb.Entity<Person>() as "Entities of type Person..."

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bricelam Are you arguing that it is not "mathematically correct"? :-P

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but I was very careful to avoid that phrase. ;)

@davidfowl
Copy link
Member

I'm generally against the internal keyword but some of those extension methods should be internal.

 - DataStore abstraction for stores
 - EntityConfiguration, a configuration model and EntityContext factory.
 - EntityServices, a static default IServiceProvider factory, matching the current K standard pattern
 - ConsoleLoggerFactory, an impl. of ILoggerFactory
@anpete
Copy link
Contributor Author

anpete commented Feb 5, 2014

Merged.

@anpete anpete closed this Feb 5, 2014
fitzchak pushed a commit to fitzchak/EntityFramework that referenced this pull request Nov 30, 2016
…SelectRows statistics. Take dotnet#2: Use the DiagnosticSource on RelationalDataReader. Take dotnet#3: Fix requested changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants