Search Results for "key"

Doctrine 2 is an object-relational mapper (ORM) for PHP 7.1+ that provides transparent persistence for PHP objects. It sits on top of a powerful database abstraction layer (DBAL). One of its key features is the option to write database queries in a proprietary object oriented SQL dialect called Doctrine Query Language (DQL), inspired by Hibernate's HQL. This provides developers with a powerful alternative to SQL that maintains flexibility without requiring unnecessary code duplication. As the term ORM already hints at, Doctrine ORM aims to simplify the translation between database rows and the PHP object model. ...

...Pay attention to splicing lambda expression trees by yourself, do not wrap your variables with ConstantExpression, otherwise, non-parameterized sql will be generated, and there is a risk of sql injection! If the entity does not explicitly specify any auto-increment columns and the primary key is of type Int16, Int32, or Int64, the default primary key is the auto-increment column. If it is not an auto-increment column, it needs to be marked with the attribute NonAutoIncrementAttribute.

...We are essentially working against those tools by sidestepping type system. First version is still invalid, since one would expect Save() method to set record's primary key after INSERT, but this change will be lost due to passing by value.

...It is robust well structured web oriented programming system that allows to create web systems (web sites) just by coding javascript. That is possible cause it uses a few server php script files that are requested by javascript to get some results. The key of this system is its structure that has to deal with nested tree objects and how it is implemented in the relational database.

littletable is a lightweight in-memory data manager of collections of Python objects, providing ORM-like access for querying and joining data using object attributes as pseudo-columns.

Simple small extensible object relational mapper with database independent key generation and paging

...All these Components use the same Meta-Base which can be definied via Attributes (Annotations) on your Business-Classes. Nevertheless differences between Xml- and Db-Serialization can be made via an enum MetaUsage (Database, Xml, Internal …). For Example you can define a Key-Column which is only used for Db-Serialization and excluded for Xml-Serialization. The same can be done with References, Delegations &c. A special Feature is that all Metadata can be read from a comfortable Object-Model (MetaLayer) for your own needs.