Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Considering Confluence 8.x upliftment, the SQL for Confluence app will no longer support the JNDI data source connections with Confluence 8.x. The already configured global data source based profiles will have to be converted to connection string profiles. Our team is working on this and will soon release the SQL for Confluence app update and the related documentation.

To know more about this change, read the FAQ below.

FAQ

Expand
titleDoes this change impact Confluence 7.x versions?

No, this change does not impact the Confluence 7.x versions.

Expand
titleWhat will be the next release version of SQL for Confluence app? Will it be compatible with Confluence 7.x versions?

The upcoming release version will be SQL for Confluence 11.x, and it will work seamlessly with Confluence 7.x (Confluence 7.4 to Confluence 7.20) versions, including support for external data sources.

Expand
titleWhat version of the SQL for Confluence app will be compatible with Confluence 8.x?

The upcoming release version SQL for Confluence 11.x will be compatible with Confluence 8.x and will drop the support for global data source profiles.

Expand
titleWhy are the global data source based profile configurations failing connection in Confluence 8.x?

With Confluence 8.x release, Atlassian has removed the support for the global data source connections, and hence the connections are failing.

Expand
titleIf the support for external data sources is removed, how do I resolve the global data source based profile configurations?

To resolve this, you need to convert the global data source profile to a local connection string profile.

To convert the global profiles to local, you have the below options:

  1. Create a new profile with the Data source name as None, and provide the connection details.

  2. Edit the configured global data source profile, change the Data source name to None and provide the connection details.

  3. Create a new local profile and choose the created profile as the Data source name in the configured global data source profiles.