Making CI's DBstuff play nice with slave/master setups

[eluser]moodh[/eluser]
[quote author="wh1tel1te" date="1302494584"]You could possibly create two config groups. Have a look at config groups here: Database Configuration

One group would be your select group (say "select"), and another would be your insert/update/delete group (say "update").

Then you could load the database class using the required group:

Code:

// I want to do some selecting!
$this->load->database('select');
// My select code goes here!

// Now I want to do some updating!
$this->load->database('update');
// My update code goes here!

More info here.[/quote]

If you read my entry thats exactly what I want to avoid since it shouldn't be needed. I'm looking for a solution that maps the correct statement against the correct database setting without having to use $DB1->db->select(), $DB2->db->insert();