Hi, I let you know, thanks!
Regards, Julien > Glad to hear it! > > @Julien Cabieces the connections API is relatively young and it may > not fit well with ORACLE table models, let me know if you run into any > issues. > > Kind regards. > > > On Wed, Nov 11, 2020 at 6:53 AM Richard Duivenvoorde > <[email protected]> wrote: >> >> On 11/10/20 9:31 AM, Alessandro Pasotti wrote: >> >> > one way to integrate a provider in the browser is to implement the >> > connections API: >> > https://qgis.org/api/classQgsAbstractDatabaseProviderConnection.html#details >> > >> > When it's done, all the generic methods implemented in the browser >> > will automatically work, see >> > >> > QgsDatabaseItemGuiProvider::populateContextMenu >> > QgsFieldsItemGuiProvider::populateContextMenu >> > >> > For a sample implementation you could have a look to the PG provider. >> > >> > You may need to subclass the GUI provider in case the base >> > functionality is not ok, the PG provider does that for some methods >> > too, so the answer is yes: you need to create a GUI provider for the >> > provider or you can choose to abstract out the PG provider and create >> > a base class if you see that there is a common ground for abstraction. >> >> Thanks Alessandro, >> >> I had a chat with Julien (Oslandia) and he told me they had some funding to >> work on the Oracle provider, and that your proposal above was exactly what >> he was going to do. So: fingers crossed :-) >> >> Regards, >> >> Richard >> >> >> >> _______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
