China
Africa
Explore chapters and articles related to this topic
Practical Approaches
Published in Nawari O. Nawari, Building Information Modeling, 2018
LINQ is the term for a set of technologies based on the integration of query capabilities directly into conventional programming languages such as C# and VB.Net. It is a part of the Microsoft .Net framework, which permits query expressions to take advantage of the rich metadata, static typing, and IntelliSense, and compile time syntax checking (Nawari, 2012c). Moreover, LINQ facilitates a unified general-purpose declarative query platform to be used for all in-memory data, not just data from external sources. The .NET LINQ provides a set of standard, general-purpose query operators that perform various types of database operations such as traversal, filter, and projection to be expressed in a direct yet declarative way in any programming language. This allows queries to be applied to any object whose type implements the IEnumerable<T> interface or the IQueryable<T> interface-based information source. In other words, LINQ has two sets of query operators: one that operates on objects of the type IEnumerable<T> and the other that operates on objects of the type IQueryable<T>, which can be called by using either static method syntax or instance method syntax.
New product design and implementation of aboleth: a mobile D&D character creator for enterprise mobile applications and metaverse
Published in Enterprise Information Systems, 2023
Victor Chang, Dan Lawrence, Le Minh Thao Doan, Ariel Qianwen Xu, Ben S.C. Liu
This implementation of a DB context is relatively lightweight; each table’s implementation of BuildEntity is called whenever the database is migrated. This happens each time the API is launched in the development environment. The properties ‘Accounts’ and ‘Characters’ are how other services access database data; the DbSet type contains a series of methods resembling those of C #‘s LINQ package, used to generate appropriate SQL queries for mapping the data into the desired output format. For the sake of simplicity, only these two tables from the schema can be accessed directly in this fashion. The data from other tables are simply included in the output model for the Character table, as there is no current use case for these tables to be accessed independently.