Third party FireDAC drivers

[Lachlan Gemmell 33]

When FireDAC was first acquired by Embarcadero there was no way for third parties to add drivers as the list of registered drivers was hard coded. Is that still the case?

 

There is reason to believe that since then the architecture may have been opened up for third parties as evidenced by the CData FireDAC Components and to a lesser extent the recent Embarcadero Encrypted SQLite FireDAC driver available through GetIt.

 

Are these "first class" FireDAC drivers or do they hack their way into the architecture in some semi-supported way?

 

If they are "first class" FireDAC drivers is the mechanism they use to register themselves with FireDAC available to all, or did CData have to get specific code changes made by Embarcadero in FireDAC for their drivers (and their drivers only) to be recognised?

 

 

Edited December 3, 2021 by Lachlan Gemmell

[Serge_G 87]

I use some of these CData Drivers.

8 hours ago, Lachlan Gemmell said:

did CData have to get specific code changes made by Embarcadero in FireDAC for their drivers

No, these are derivation of  FireDAC.Phys.ODBCBase.pas and FireDAC.Phys.ODBC.pas and some registering classes 

FDPhysManager().RegisterRDBMSKind
FDPhysManager().RegisterDriverClass