Do my “dal” and “fileHandler” interfaces overlap?
I want my program to:
Strategy for backwards compatibility of persistent storage
In my experience, trying to ensure that new versions of an application retain compatibility with data storage from previous versions can often be a painful process.
DDD using an ORM and a Active Directory Server for Persistence
With Domain Driven Design one would model out the domain. One would then use an ORM of some sort to take care of the persistence. Say you have a Product entity which has a Name, SKU and an Owner. This will be modelled and when a new Product gets created you need to pass in all 3 fields as parameters into the constructor.
DDD using an ORM and a Active Directory Server for Persistence
With Domain Driven Design one would model out the domain. One would then use an ORM of some sort to take care of the persistence. Say you have a Product entity which has a Name, SKU and an Owner. This will be modelled and when a new Product gets created you need to pass in all 3 fields as parameters into the constructor.
DDD using an ORM and a Active Directory Server for Persistence
With Domain Driven Design one would model out the domain. One would then use an ORM of some sort to take care of the persistence. Say you have a Product entity which has a Name, SKU and an Owner. This will be modelled and when a new Product gets created you need to pass in all 3 fields as parameters into the constructor.
DDD using an ORM and a Active Directory Server for Persistence
With Domain Driven Design one would model out the domain. One would then use an ORM of some sort to take care of the persistence. Say you have a Product entity which has a Name, SKU and an Owner. This will be modelled and when a new Product gets created you need to pass in all 3 fields as parameters into the constructor.
DDD using an ORM and a Active Directory Server for Persistence
With Domain Driven Design one would model out the domain. One would then use an ORM of some sort to take care of the persistence. Say you have a Product entity which has a Name, SKU and an Owner. This will be modelled and when a new Product gets created you need to pass in all 3 fields as parameters into the constructor.
Is there a detriment to using SQLite over a pList for persistence?
I’m making a fairly simple application and I’ve got a settings menu that stores times and some boolean values. I have the application storing and retrieving data already but I started to wonder if SQLite was a bad choice.
Is there a detriment to using SQLite over a pList for persistence?
I’m making a fairly simple application and I’ve got a settings menu that stores times and some boolean values. I have the application storing and retrieving data already but I started to wonder if SQLite was a bad choice.