Constructor remains backwards compatible.

Should this always return$this->latestPdoTypeUsed if we want to know the actual PDO that was used to run the query?

$this->readWriteType does not tell the real read/write type that was actually used.
If you run the following query, it sets thereadWriteType towrite, but it still uses the read connection as it's a select query.

DB::connection('pgsql::write')->table('users')->count();

@avosalmon, when using the explicit::write or::read connection, although both the read and write PDO properties are populated, they contain the same PDO instance once both resolved, for example:

// file: config/database.php'connections' => ['sqlite' => [// ...'write' => ['database' =>env('DB_DATABASE',database_path('database.write.sqlite')),            ],'read' => ['database' =>env('DB_DATABASE',database_path('database.read.sqlite')),            ],// ...        ],

Artisan::command('dev',function () {DB::connection('sqlite')->select('select 1');DB::connection('sqlite')->statement('select 1');dump(DB::connection('sqlite')->getRawReadPdo() ===DB::connection('sqlite')->getRawPdo());DB::connection('sqlite::read')->select('select 1');DB::connection('sqlite::read')->statement('select 1');dump(DB::connection('sqlite::read')->getRawReadPdo() ===DB::connection('sqlite::read')->getRawPdo());DB::connection('sqlite::write')->select('select 1');DB::connection('sqlite::write')->statement('select 1');dump(DB::connection('sqlite::write')->getRawReadPdo() ===DB::connection('sqlite::write')->getRawPdo());});

If we don't respect thereadWriteType value, then it could incorrectly say you are using thewrite PDO when you are using theread PDO. Keep in mind that we are talking about the actual configured PDO regardless of what property it is attached to.

In your example,DB::connection('pgsql::write')->table('users')->count(); is using theconfigured write connection, which is what we care about as a consumer of the read / write type.