Where do databases fit into object-oriented design? Lets say for example I had a articles database simple straight to the point, my use case diagram had scenarios for search articles, view article, and create article.
Should I have an article class with a connection to the database within the class or just a global database class so that other classes say user class can access the same connection?
Also should I use tables as objects such as article being it's own data object then having a class like ArticleApi for CRUD operations?
Another also if anyone has any start-to-finish object-oriented analysis and design tutorials that would be great.
Sorry for such a novice question I come from procedural programming practices and trying to move into the object-orientation part of software development.