I have developed a set of related modules. Over time, they have eveloved with many changes & enhancements.

With each module upgrade, a new DataProvider file was added to adapt the database structure appropriately. Now, there have been some breaking changes to module & database structure. I have a situation where Module 2 depends upon Module 1. However, the latest version of Module 1 has dropped a DB column and Module 2 has adapted accordingly.

For a user upgrading to latest versions, there is no problem. But for a user installing these modules from scratch, Module 2 instllation raises SqlExceptions because it is installed after Module 1 whose installation created and dropped that DB column.

Now, earlier DataProvider files in Module 2 still refer that column, and hence raise exceptions.

I have seen for the core DNN installation, all appropriate DataProvider files are executed when upgrading. However, specific DNN versions when installed from scratch execute just one single DataProvider file.

What this means is that there is some setting, through which you can mark a particular version. When upgrading, it is normal. But you can provider a separate DataProvider file which sets up the database cleanly in case a clean install is made.

Is this functionality available for Modules also?? Can I organize DataProvider file into such sets that are exceuted for upgradation or clean installation?

Hi Ian, you did not understand my problem properly. Let me take an example.

A User installs DNN 4.5.0. Now, if he upgrdaes to DNN 5.0.0, all DataProviders > 4.5.0 & <= 5.0.0 executes. But for a new user installing DNN 5.0.0, only a single DataProvider 5.0.0 executes. However, a User installing a clean DNN 4.9.0 also has DataProviders from (probably) 4.6.0 to 4.9.0 executing.

If you monitor carefully, DNN core seems like having a setting, where a a core version is specified as a major one. Users upgrading from previous versions have their DBs upgraded appropriately. However, for the major version, the core team provides a separate DataProvider which sets up the DB from scratch for that version. This helps clean-up DataProviders after a series of upgrades.

My question is can I do this with module DataProviders also?? I hope a core team member understands what I mean!!

Looks like I need to go for a custom solution.

Anyways, someone was able to understand what I meant. If DNN team thinks (and it should think so), that this could be a common requirement, so can I reuqest this as an enhancement on Gemini??