dorm, “The Delphi ORM” and Spring for Delphi Framework

Great news for all the dorm and Spring4D users!

As you probably know, finally has been announced the official Spring framework for Delphi.

There is a lot of good technology in Spring4D!

So, I’m glad to announce that in a future version (hopefully, the next one) dorm, “The Delphi ORM” will use Spring4D and will become the ORM part of Spring4D.

So, dorm will be part of the Spring4D framework.

More info to come, so stay tuned.

10 thoughts on “dorm, “The Delphi ORM” and Spring for Delphi Framework

  1. Can I use this framework with any database that I use in my project?

    As I was looking about this features, that is a great framework!

  2. Can I use this framework with any database that I use in my project?

    As I was looking about this features, that is a great framework!

  3. Not “any” but only the databases that actually have a persistenceadapter. Currently there are the following adapter: Firebird, Interbase, SQLite, MSSQLServer

  4. Not “any” but only the databases that actually have a persistenceadapter. Currently there are the following adapter: Firebird, Interbase, SQLite, MSSQLServer

  5. Hi,
    thank you for this great project. I our company we adopted Spring4D a lot. May I ask what is the status of the adoption of DORM in Spring – till this time I see no sign of it in public. We would even be able to participate. I have analyzed the situation and have some notes on it. I need to say it is not so straighforward and has couple of different points of view. Please let me know about you current perspective on this question.

  6. Hi,
    thank you for this great project. I our company we adopted Spring4D a lot. May I ask what is the status of the adoption of DORM in Spring – till this time I see no sign of it in public. We would even be able to participate. I have analyzed the situation and have some notes on it. I need to say it is not so straighforward and has couple of different points of view. Please let me know about you current perspective on this question.

  7. Great, we are also in contact with Stefan, one of our colleagues made adoption to next gen compilers during fall.

    There are different points of view on the situation. On one side, it shouldn’t be so difficult to adopt the code to take advantage of the Spring, althrough fully interfaced based approach will need some minor changes in the use of DORM (like the way adapters, mapping strategies etc. are registered and used).
    On the other side I suppose the bigger advantage would be in using interfaced collections from Spring instead of TObjectList etc. It also wouldn’t be so difficult, for my purpose I made simple wrapping class implementing spring collections and it works quite well.
    But to hold the idea of dependency injection, the best of all would be of course using interfaces instead of object in relational mapping. And here starts problems, because RTTI is weakly supported on interfaces. For example interfaces do not have fields nor properties. Attributes are not supported at all.
    DORM session is very general in case of objects, but it is not able to work with interfaces at the moment. Mapping must be performed some other way also. Do you thing this is the direction you would like DORM to evolve?

  8. Great, we are also in contact with Stefan, one of our colleagues made adoption to next gen compilers during fall.

    There are different points of view on the situation. On one side, it shouldn’t be so difficult to adopt the code to take advantage of the Spring, althrough fully interfaced based approach will need some minor changes in the use of DORM (like the way adapters, mapping strategies etc. are registered and used).
    On the other side I suppose the bigger advantage would be in using interfaced collections from Spring instead of TObjectList etc. It also wouldn’t be so difficult, for my purpose I made simple wrapping class implementing spring collections and it works quite well.
    But to hold the idea of dependency injection, the best of all would be of course using interfaces instead of object in relational mapping. And here starts problems, because RTTI is weakly supported on interfaces. For example interfaces do not have fields nor properties. Attributes are not supported at all.
    DORM session is very general in case of objects, but it is not able to work with interfaces at the moment. Mapping must be performed some other way also. Do you thing this is the direction you would like DORM to evolve?

Comments are closed.