3 ms·

Database schema is not actually the most important thing i need to be a productive programmer. What i need more is a smart ORM which gives me tool to calculate

Database schema is not actually the most important thing i need to be a productive programmer. What i need more is a smart ORM which gives me tool to calculate dependent fields based on other fields changes, then automatically store it on a field. Secondly, it should provide smart many2many relationship with smart caching techniques. Those are features that prevents me to continue with RoR.

deleted 6y ago
[deleted]
jolmg 6y ago
> What i need more is a smart ORM which gives me tool to calculate dependent fields based on other fields changes, then automatically store it on a field. Is the ORM really the layer where you want those features? Because at the RDBMS layer you have views, materialized views, and triggers for that. If you really want this at the ORM level, you can do it in RoR with e.g. model callbacks or custom attribute writers. > Secondly, it should provide smart many2many relationship with smart caching techniques. Those are features that prevents me to continue with RoR. RoR's many2many associations already do caching, though. I don't see what you're lacking with RoR on either point.
sorenbs 6y ago
Hi there, I think Prisma might cover "smart many2many relationships". What exactly do you mean by smart caching techniques? Prisma is applying the dataloader pattern from GraphQL automatically under the hood, which we find to be a much easier thing to reason about compared to all the complexity of multi-tiered caching in Hibernate. The dependent field requirement is super interesting, and something we will tackle in the future based on Change Data Capture. With Prisma you will be able to write a simple declarative data transformation, and the system will automatically keep the field up-to-date, even if the database is changed by another application, or manually by a user. Hope that makes sense? :-)

deleted 6y ago

[deleted]

jolmg 6y ago

> What i need more is a smart ORM which gives me tool to calculate dependent fields based on other fields changes, then automatically store it on a field. Is the ORM really the layer where you want those features? Because at the RDBMS layer you have views, materialized views, and triggers for that. If you really want this at the ORM level, you can do it in RoR with e.g. model callbacks or custom attribute writers. > Secondly, it should provide smart many2many relationship with smart caching techniques. Those are features that prevents me to continue with RoR. RoR's many2many associations already do caching, though. I don't see what you're lacking with RoR on either point.

sorenbs 6y ago

Hi there, I think Prisma might cover "smart many2many relationships". What exactly do you mean by smart caching techniques? Prisma is applying the dataloader pattern from GraphQL automatically under the hood, which we find to be a much easier thing to reason about compared to all the complexity of multi-tiered caching in Hibernate. The dependent field requirement is super interesting, and something we will tackle in the future based on Change Data Capture. With Prisma you will be able to write a simple declarative data transformation, and the system will automatically keep the field up-to-date, even if the database is changed by another application, or manually by a user. Hope that makes sense? :-)