EntityDAC

EntityDAC is an ORM for Delphi with LINQ support. It provides a powerful framework that allows to perform object-relational mapping of database objects to Delphi classes with full support for encapsulation, inheritance, polymorphism and other OOP features.

  1. Support for Enum and Complex types

    Entity Developer allow to create model with enum and complex types. It would by nice, if generated delphi code (model), contain code necessary to operate on this types.

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Mobile Support

    Would like to see Mobile Support for Android and iOS.

    33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Eagerly loading

    Eagerly loading (.include method) would allow to optimize db usage in more complicated queries.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add an edition including data access components.

    Add a special Developer Edition, that will be an inclusive solution for database application development, and will include not only the ORM engine - EntityDAC, but database connectivity tools as well (some of Devart Data Access Components, for example, UniDAC).

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow validation/business rules

    When using EntityDac, it would be great to be able to define business rules on entities (validations).

    Those would be enforced by the framework when updating an entity. Perhaps they could be done in a single transaction.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add support for database domains and stored procedures

    Would be nice to map SQL stored procedures and domains into the code.

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Multiple transaction support

    According to new multi-thread version, multiple transaction support would be facilitation.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. support SMALLSERIAL postgresql type

    it will be good if you support postgresql smallserial type

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Native Code Methods

    We use EntityDAC with RAD Studio XE7. It would be real handy to have a way to include native language code mapped to methods in the Entity model.

    It seems that the current definition of methods are limited to SQL Server stored functions or procedures, or some format of an SQL statement.

    In the case that calculated values or operations are needed that are beyond the scope of SQL syntax (ie. a Windows API call or local file read operation), it would be super handy to have custom methods on an entity that permit native Pascal code.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add support for Linq Insert / Update / Delete / Script

    Would be great to be able to create Linq queries for other operations than Select. I would like to be able to construct a full script using Linq. I could then avoid using damned Stored Procedures!

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Entity DAC should natively support ElevateDB

    Entity DAC should natively support ElevateDB. TMS's Aurelius currently natively supports ElevateDB and Nexus.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Database Provider handles Engine-specific Capabilities

    Database Provider handles Engine-specific Capabilities

    Actual Entity-Developer creates engine-specifics Models. (I.E.: in mysql backticks operator for restricted words). This makes it impossible to use the same modell for different database engines.

    I would expect that the database provider uses engine specific capabilities to ensure interchangeability.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Code-mapped objects support

    I share my domain model classes among other projects, Sometimes, the table-names are not the same as i have to accomodate into an existing customer database.

    Would be nice if to map TObject descendants through the code the way we can do with TEntity descendants.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Support for detach an entity from data context (manual memory management)

    Add support for detach an entity from the data context so, manual destroying of the entity instances can be done. Suggestion: add a parameter "Detached" to methods like GetEntity of the data context and Linq Query. Create a method "Detach" to data context class.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Support for unidirectional association mapping

    As of EntityDAC v.2.1 all mapped associations are bi-directional. That is: in order to map TDepto and TEmployee associatiation, one must to declare the association on both classes. However, there is situations where this approach is not desirable.

    Unidirectional associations (e.g. @OneToMany annotations on Java JPA) would be great.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

EntityDAC

Feedback and Knowledge Base