Hi,
If you use datalists across more than one servers and each solution have a different database server you will get in problem as you cannot edit a connection once it has been created. That is a problem.
We need a way to handle stages on datalist connections.
In a perfect world you should be able to add stages to datalist connections so that the datalists will not break when the database is deployed to another stage. If you would add a "+" sign on each connection, where you associate each connection to a stage server/domain or..?
Actually this also applies to the default connection - the Dynamicweb DB connection, which you cannot edit.
Where are the actual connection stored? At the moment I use this SQL script to change which connection is used in the datalists:
--- Datalist --- --- Update connection db name after database copied from one server to another -- UPDATE DMViewSetting SET ViewSettingConnectionDBName = 'liveServerDatabaseName' WHERE ViewSettingConnectionDBName ='developmentServerDatabaseName'
This is not good.
Med venlig hilsen/Best regards,
Sten Hougaard
Webudvikler