Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

CRUD

CRUD refers to the four major functions implemented in database applications, namely create, retrieve, update and delete.

The CRUD functions are the user interfaces to databases, as they permit users to create, view, modify and alter data. CRUD works on entities in databases and manipulates these entities. Any simple database table enforces CRUD constraints.

For more information, go to Implementing Basic CRUD Functionality with the Entity Framework.

Entity

An entity is a class object that exists in memory. When you build/launch your project the entity is then mapped to a data table in the database.

Entity Framework Code First

In the Code-First approach, you focus on the domain of your application and start creating classes for your domain entity rather than design your database first and then create the classes which match your database design.

• For more information, go to Entity Framework Code First

• To see how to create a Model in Entity Framework, go to Creating a Model - EF6

Odata

OData helps developers focus on Business Logic while they create RESTful APIs without the need to define request and response Headers, HTTP Methods, Status Codes, Media Types, URL Conventions, Payload Formats, and more.

Read more in the Odata reference article.

Razor

Razor is a markup syntax that lets you embed server-based code (Visual Basic and C#) into web pages.

Read more in the Razor reference article.

Temporal tables

A system-versioned temporal table is a type of user table designed to keep a full history of data changes to allow easy point in time analysis.

Use cases for temporal tables include:

• Auditing all data changes and performing data forensics when necessary.

• Reconstructing state of the data as of any time in the past.

• Calculating trends over time.

• Maintaining a slowly changing dimension for decision support applications.

• Recovering from accidental data changes and application errors.

Read more in the Temporal table reference article.

For more information, go to Temporal Tables - SQL Server

Uniform Resource Identifier

The Uniform Resource Identifier (URI) is intended to identify abstract or physical resources on the Internet. What these resources are supposed to be can vary according to the situation. It can thus be, a website, for example. However, email senders and recipients can also be identified via URI. Applications use the unambiguous designation to identify a resource or to request data from it.

URI Syntax

A URI consists of up to five parts. However, only two of these are mandatory.

• scheme: Gives information about the protocol being used.

• authority: Identifies the domains.

• path: Shows the exact path to the resource.

• query: Represents a request action.

• fragment: Refers to a partial aspect of a resource.

Only scheme and path must appear in every identifier. In the URI syntax, all components are listed successively and separated by specific, predefined characters.

Source: IONOS

URL

The abbreviation “URL” stands for “Uniform Resource Locator”. It is a subspecies of uniform resource identifiers (URIs). URL structure also corresponds to URI syntax.

Identifiers make it possible to locate resources using a unique identifier, both locally and worldwide on the internet. As an “Identifier” subspecies, URLs are sometimes used interchangeably with the term “Internet address”. This is because of the URLs main use: addressing web pages. However, URLs are not limited just to this function. Files in the local file system can be localized using URLs, for example. This means that every internet address is a URL but not every URL is an internet address.

Source: IONOS