Class Table Inheritance: do child tables need a primary key?
I’m using the Class Table Inheritance architecture with my application and have read Fowler. When mapping my database tables to classes in code, I’ve realized I have no need for an “ID” property on my derived classes, and, in fact, it can cause issues if it has the same name because it hides the base class property.
Class Table Inheritance: do child tables need a primary key?
I’m using the Class Table Inheritance architecture with my application and have read Fowler. When mapping my database tables to classes in code, I’ve realized I have no need for an “ID” property on my derived classes, and, in fact, it can cause issues if it has the same name because it hides the base class property.
ActiveRecord equivalent in Java [closed]
Closed 9 years ago.
Implementing a NoSQL and RDBMS compatible DAO
What would be the correct way to design a DAO which implementation is first going to be targeting a MS SQL database with a STAR model, but yet, business requirements specify the application must be flexible enough that it would be able to be migrated to a NoSQL database in the future if required. Which type of NoSQL, no idea…
Implementing a NoSQL and RDBMS compatible DAO
What would be the correct way to design a DAO which implementation is first going to be targeting a MS SQL database with a STAR model, but yet, business requirements specify the application must be flexible enough that it would be able to be migrated to a NoSQL database in the future if required. Which type of NoSQL, no idea…
Implementing a NoSQL and RDBMS compatible DAO
What would be the correct way to design a DAO which implementation is first going to be targeting a MS SQL database with a STAR model, but yet, business requirements specify the application must be flexible enough that it would be able to be migrated to a NoSQL database in the future if required. Which type of NoSQL, no idea…
Implementing a NoSQL and RDBMS compatible DAO
What would be the correct way to design a DAO which implementation is first going to be targeting a MS SQL database with a STAR model, but yet, business requirements specify the application must be flexible enough that it would be able to be migrated to a NoSQL database in the future if required. Which type of NoSQL, no idea…
Implementing a NoSQL and RDBMS compatible DAO
What would be the correct way to design a DAO which implementation is first going to be targeting a MS SQL database with a STAR model, but yet, business requirements specify the application must be flexible enough that it would be able to be migrated to a NoSQL database in the future if required. Which type of NoSQL, no idea…
Does ORM at any point become a “requirement” for RESTful API?
I’ve started building a RESTful API in PHP’s Slim framework. The framework appealed to me because of its light-weight design and routing features. I am using PostgreSQL for the database.
Unit testing Eloquent outside of Laravel
How can I unit test my Eloquent models when I’m using the ORM outside of Laravel? What I’m hoping to do it run tests on each model but somehow mock the database connection/query/builder(?) object.