Home/ Questions/Q 8795551
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T23:24:44+00:00

I’m currently designing a game that utilises CodeIgniter, but I don’t think the singleton

  • 0

I’m currently designing a game that utilises CodeIgniter, but I don’t think the singleton approach to models is the way I want to handle the game-related objects in the DB.

I want to use a CodeIgniter Model class to handle the basic CRUD operations of the objects, but have the objects as PHP Classes.

Example:

 $this->load->model('playermodel');
 $player = $this->playermodel->get($player_id); // Returns a Player object

 // Call modifying operations on the player (equip item, take damage etc.)

 $this->playermodel->save($player); // Commits updated Player back to DB

 $player2 = $this->playermodel->create(); // Basically calls new Player()

I’m fairly new to CodeIgniter, would something like this be going against any kind of CodeIgniter or MVC design rules? And if so, could anyone recommend me another approach to my problem?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    What you currently have is a strange interpretation of data mapper pattern (do not confused with CI’s ORM with same name, which instead implements active record pattern).

    The idea would be to separate the domain logic from the interaction with storage abstraction. For simplified code example, you can read this post.

    Only major problem, that i sea with your implement, is that your mapper also contains logic for creation of instance. Thus, it has acquired also the characteristics of a factory (or maybe, builder .. depends on your particular use-case). This would violate single responsibility principle.

    But non of this is against CI’s design rules. Because it has none.

    • 0