ActiveRecord is too limited. However, I am in a difficult situation in terms of the views of each team member regarding the use of ORM. We currently use the very simple ActiveRecord with regret, which I'm talking about, written mostly by hand with some basic generation of code. I would like to create a new DAL for us, but avoiding ActiveRecord restrictions, so there is more DDD. The points I fight at are (both old developers and I are very young):
Lead developer
- It is in favor of stored procedures, but it is not sequential ... some just get a table, for example. SELECT * FROM Company, and some get SELECT C. *, O.OtherTableValue FROM Company C ... (very frustrating)
- Not aware of the benefits of some of the latest ORM tools.
- Will not be attached to any instrument as its "too restrictive", and if you have questions, what are you doing?
Dba
- I do not like dynamic SQL
- Don't like SELECT *
I am not saying that this is beyond limits, especially specifying them otherwise. I believe that we could significantly improve our effectiveness with ORM, but it is very difficult to convince them otherwise. If I could give evidence to some of these areas, I could convince them, even implementing them under the covers, not knowing them proactively, and then seeing the benefits.
What advice can you give to help my situation? I believe that many developers are faced with this and cannot choose which architecture they would like to use.