Skip to content

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.

EntityDAC

Categories

JUMP TO ANOTHER FORUM

22 results found

  1. Hi, I am just working on an API, accessing my database with the help of your EntityDAC component.
    When passing back the information in JSON format I have to manually create a JSON type, copy the EntityType values in it and pass it back to the webserver.
    It would be great if there would be a command to just transform the MappedEntity or the MappedEntityLists to a corresponding JSON structure.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. TEntityConnection does not have any pooling options... documentation doesn't show how either...

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Received the following error when attempting to use LINQ on a many to many relation: Message: TQueryConverter.TranslateMemberLink: TMetaAssociationManyToMany is not implemented yet (C:\Apps\Devart\EntityDAC\src\EntityDAC\Source\EntityDAC.Linq.Converter.pas, line 268)

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Update database method

    Would be great to have a method to update the changes in the database from the model.
    So once the change in the model has been made, this method is called something like this

    Connection.UpdateDatabase (nil, [moCommitEachStatement]);

    and updates to the database are updated.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. EntityDAC suport DBF files and SAP Advantage database server and local

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. it will be good if you support postgresql smallserial type

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. According to new multi-thread version, multiple transaction support would be facilitation.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Eagerly loading (.include method) would allow to optimize db usage in more complicated queries.

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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.

    41 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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!

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Would be nice to map SQL stored procedures and domains into the code.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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.

    25 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Would like to see Mobile Support for Android and iOS.

    47 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1
  • Don't see your idea?