Menu
We're all familiar with basic ORM with relational databases: an object corresponds to a row and an attribute in that object to a column, though many ORMs add a lot of bells and whistles.
I'm wondering what other alternatives there are (besides raw access to the data). Alternatives that just work with relational databases would be great, but ones that could work with multiple types of backends besides just SQL (such as flat files, RSS, NoSQL, etc.) in a uniform manner would be even better. I'm more interested in ideas rather than specific implantations and what languages/platforms they work with, but please link to anything you think is interesting.
889
To avoid the mapping problem you have two alternatives. Either you use the relational model in memory, or you don't use it in the database.
DAL (Data Access Layer):It is a layer that handles all your data needs. But this is different from ORM. Actually, this may use ORM internally for any RDBMS communication. Although DAL can be designed without using any ORM also.
There are many types of ORM languages like Django ORM, Dapper ORM, JOOQ ORM, SQL Alchemy, etc.
Your basic choices are:
133
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
