New Book: Introducing Delphi ORM

I would like to share with you that my new book has reached the production stage and will be available in September by Apress.

The book is about Object Relational Mapping in Delphi and explores TMS Aurelius– an excellent ORM solution for Delphi developers.

I would, also, like to cordially thank Wagner Landgraf and Nick Hodges who were the tech reviewers of the manuscripts.

Nick (who does not need any introductions) always shares his deep experience and has been very supportive while I was writing this book.

Wagner (the creator of TMS Aurelius) has been guiding me with his expertise and suggestions to produce a presentation of Aurelius based on real-life situations.

Thank you both.

I hope you enjoy the book and I am looking forward for your feedback.

5 comments

  1. I am confused as to why you titled the book ‘Introducing Delphi ORM’. The title led me to mistakenly believe you wrote the book about Daniel Teti’s DORM (https://github.com/danieleteti/delphi-orm). I would have called it ‘Introducing TMS Aurelius’.

    BTW, ‘and excellent ORM’ should read ‘an excellent ORM’ .

    Great to see more Delphi books being published. I am looking forward to reading your MVVM book.

    1. Hi Larry,

      I am confused as to why you titled the book ‘Introducing Delphi ORM’. The title led me to mistakenly believe you wrote the book about Daniel Teti’s DORM (https://github.com/danieleteti/delphi-orm). I would have called it ‘Introducing TMS Aurelius’.

      I know Daniele’s DORM. There was a discussion with Apress and the decision is to keep this title.

      BTW, ‘and excellent ORM’ should read ‘an excellent ORM’ .

      Thanks for picking this up. I corrected it.

      Great to see more Delphi books being published. I am looking forward to reading your MVVM book

      Thanks. I am looking forward to your feedback.

  2. Just bought your book to learn about Aurelius but have the feeling it’s a class for people already knowledgeable with Aurelius.
    Anyway, one thing that should be corrected immediately are the Database models for Chapter 2, as well as their Class representations: TUser and TPost as shown in diagrams and source code do not at all match the example you try to show while using aurelius and doesn’t help the reader.
    In Aurelius examples, you introduce columns/field like Image, Date, etc… that are not represented in the diagrams nor are there in the “original” TUser and TPost examples rendering your source code unusable except if the user goes back and forth to the diagram and write new properties on them constantly.
    It would be nice to have diagrams matching what you try to represent with Aurelius.
    Thanks

    1. Hi Steve,
      thanks for reading my book and for the comments.

      …but have the feeling it’s a class for people already knowledgeable with Aurelius

      The book does not attempt to replace the technical manual TMS already provides. It does explain some concepts not discussed in the technical manual but it assumes that the reader has already gone through the manual. It is pointless to try to write a manual of that nature as we have one coming from the developers. What the book does is to provide some theoretical background to ORM concepts, show how Aurelius approaches them and, then, use them in a real-life application.

      Anyway, one thing that should be corrected immediately are the Database models for Chapter 2, as well as their Class representations:…

      I believe you refer to Fig. 2-14 and the code in the following section. I can see your point about the fields in the figure and the code. Fig 2.14 is borrowed from Fig. 1-1. You are right that the “Many-to-One Association” section should use database fields that match exactly Fig. 2-14. However, the following sections are fine because they introduce new fields that do not show in Fig. 2-14 or in any other figures. This is because all the work is done in the code and Fig. 2.14 works as the conceptual starting point to build the classes (assuming one uses the database-first approach). Hope this clarifies the situation.

      Thanks again for getting back to me. Please feel free to share your feedback or any other questions you may have.

      Regards,
      John

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.