Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Added driver map getter #340
We can think of several situations where a read access to the supported drivers is required. I personnaly need it in the following use cases :
This PR just adds a getter for that list. As it is a harmless and non-BC-break change, it would be great if it could be merged also into the 2.3 version.
@beberlei sorry, I've been busy all day. I will update the PR first thing tomorrow morning -- I can't now :/ -- if you think it's a good addition to the driver manager. But I'm afraid it won't solve all the issues I'm dealing with. Generating migration classes for all the available platforms implies being able to list those platforms and classify them by driver, and as far as I know, only the driver classes can provide the necessary informations on that subject.
On the other hand, thinking about the remark you made on the distinction between drivers and platforms, I realized that despite some of them having mutliple platform versions (actually only sqlsrv, but it could grow later), the driver classes always return the same single platform class. Unless I've missed something, there's no way to get a connection to SQLServer for the particular 2005 or Azure version, without creating a custom driver class which returns the corresponding platform. Which leads me to that question : won't it be a good thing to add an optional platform version parameter to the array passed in the