Unit testing database access layer?

Depending on who you ask, it always makes sense to test code. That said, what you're doing here is pretty straight forward and might not need testing. However, I would argue that even if it's difficult to set up a test database, you will most likely need it later anyway, so you might as well do it now when you're not trying to do something complicated.

Also, it's find that the schema is evolving. It's almost inevitable that there will be major database changes over time and you just have to roll with it.

Unit tests (i.e. Without a database), not IMO. Integration tests generally I think it is a good idea.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.