Ticket #28 (closed Feature Request: fixed)

Opened 19 months ago

Last modified 19 months ago

Active Record configuration placement is misleading.

Reported by: JAAulde Owned by: JAAulde
Priority: major Milestone: 1.0
Component: Version:
Keywords: Cc:

Description (last modified by JAAulde) (diff)

Currently the configuration for turning on or off Active Record is in the separate DB connection config arrays in the database.php configuration file. However, given the manner in which the CI_DB class is instantiated, only the configuration for the first DB loaded makes any difference.

If the config for the first DB loaded has AR on, AR will be on for all. If it is off, AR will be off for all. Considering most people either want it for all or not anyway, it should become a single config outside of the specific database connection configs.

Changing this will smooth the fix for a separate major ticket (#29), so I am making this major.

Change History

Changed 19 months ago by JAAulde

  • description modified (diff)

Changed 19 months ago by JAAulde

I moved the configuration out of the per-db configs and into the main config.php config file. I also updated the pertinent portions of the user guide.

Committed this to trunk but could not merge it to 1.0--opened ticket #32.

I tested these changes and it works well. This ticket can be closed after the merge to 1.0.

Changed 19 months ago by JAAulde

  • status changed from new to closed
  • resolution set to fixed

Closing even though #32 is not done. Clarification received in IRC #blueflame made me more comfortable.

Note: See TracTickets for help on using tickets.