Creational Design Patterns in Modern C++ - Database Framework Usage

The lecture discusses the drawbacks of using preprocessor directives for creating database instances, highlighting issues with code maintenance and runtime flexibility. It suggests using conditional statements as an alternative but notes that this still poses challenges. The lecture emphasizes the need for consistent database usage and introduces the factory method as a potential solution to improve code structure and enforce consistency.

What is a major drawback of using preprocessor directives for database instance creation?

• They fix the database choice at compile time.

• They allow runtime flexibility.

• They make the code easy to maintain.

• They automatically handle new database types.

Why is using conditional statements not a significant improvement over preprocessor directives?

• They automatically update for new databases.

• They prevent runtime database selection.

• They still result in complex and hard-to-read code.

• They eliminate the need for macros.

What issue arises when users create database instances directly?

• It allows mixing of different database classes.

• It ensures consistent database usage.

• It simplifies the code structure.

• It enforces the use of SQL Server only.

What is the purpose of implementing a factory method for database class instances?

• To allow users to choose any database class.

• To ensure instances are created from the same database set.

• To make the code more complex.

• To eliminate the need for any conditional logic.

How does the factory method help in resolving the issues with the previous approaches?

• By making the code less readable.

• By allowing direct instance creation by users.

• By using more preprocessor directives.

• By ensuring consistent and correct instance creation.