1. Content on the page is inconsistent due to conflict in css classes
2. Unable to fetch data source profiles for the macro users
1. Content on the page is inconsistent due to conflict in css classes
2. Unable to fetch data source profiles for the macro users
In version 10.1:
Read more in the full release notes.
In version 10.1:
Read more in the full release notes.
SQL for Confluence (Pro Edition) is now compatible with Confluence 7.0
SQL for Confluence (Pro Edition) is now compatible with Confluence 7.0
What’s new in v10.0?
Read more in the full release notes.
What’s new in v10.0?
Read more in the full release notes.
We've made massive investments in infrastructure and testing frameworks for our Data Center apps to ensure that they will scale to meet the needs of your enterprise team. SQL for Confluence Data Center has been rigorously tested and vetted for consistent, efficient, and reliable performance at scale.
For more information, read the full release notes.
Our server apps have always been Data Center compatible, and with the release of Atlassian’s new Data Center approved apps program, we've made massive investments in additional infrastructure and testing frameworks for our Data Center apps to ensure that they will scale to meet the needs of enterprise teams. These apps have been rigorously tested and vetted for consistent, efficient, and reliable performance at scale.
If you’re currently using Confluence Data Center or thinking about upgrading, check out the Data Center approved version of SQL for Confluence Pro Edition.
Additionally, this release also includes some minor fixes.
For more information, read the full release notes.
What's new in version 9?
Configure your data sources with ease — We've completely redesigned the admin configuration page to make it easier to connect to your SQL databases. Say goodbye to messy strings and hello to a straightforward, form-based setup.
Monitor data source connections in real time — Ensure your data sources are set up correctly from the start and stay connected with enhanced editing and visual connectivity indicators.
Connect to unlimited data sources — There is no longer a limit to the number of data sources you can connect to and save. Yes, you read that right! Unlimited data sources = unlimited business intelligence insight.
Read more in the full release notes.
What's new in version 9?
Configure your data sources with ease — We've completely redesigned the admin configuration page to make it easier to connect to your SQL databases. Say goodbye to messy strings and hello to a straightforward, form-based setup.
Monitor data source connections in real time — Ensure your data sources are set up correctly from the start and stay connected with enhanced editing and visual connectivity indicators.
Connect to unlimited data sources — There is no longer a limit to the number of data sources you can connect to and save. Yes, you read that right! Unlimited data sources = unlimited business intelligence insight.
Read more in the full release notes.
Release Notes 8.0 (important!)
SQL-237: Excessive perm gen memory use when using profile defined data sources. Application server defined data sources do not have a problem.
A new macro called sql-file is provided to enable user scenarios related to macro-security. It only allows accessing specifically authorized scripts stored on the Confluence server file system. This provides more flexibility for administrators to selectively grant general access to the results of specific SQL scripts on pages without edit restrictions or with less restrictive edit restrictions. This is accomplished using standard Macro Security for Confluence parameter control configurations.
The following allows the authorized.sql script located in the <confluence home>/script directory to be run from any page against any data source. No other SQL scripts can be run.
sql-file=*ANY sql-file.datasource.*=*ANY sql-file.file.authorized.sql=*ANY
See Advanced date sorting for more details.
A new macro called sql-file is provided to enable user scenarios related to macro-security. It only allows accessing specifically authorized scripts stored on the Confluence server file system. This provides more flexibility for administrators to selectively grant general access to the results of specific SQL scripts on pages without edit restrictions or with less restrictive edit restrictions. This is accomplished using standard Macro Security for Confluence parameter control configurations.
The following allows the authorized.sql script located in the <confluence home>/script directory to be run from any page against any data source. No other SQL scripts can be run.
sql-file=*ANY sql-file.datasource.*=*ANY sql-file.file.authorized.sql=*ANY
See Advanced date sorting for more details.
Fix a dependency problem which may cause installs on Confluence 5.x to fail.
This release fixes a security exposure for customer using Macro Security for Confluence to secure use of the sql macros.
Administrators can now configure a data source via plugin configuration. These are referred to as data source profiles. These can be used just like the normal application server defined data sources. A key benefit is that a server restart is not required to make the data source active for use by macros. From a macro use perspective, they can be referenced just like application server datasources.
Data source profiles can add before and after SQL that automatically gets inserted around the macro defined SQL.
Macros can reference a data source (dataSource parameter) that gets redirected to a specific application server data source defined by the administrator. The benefit of this is to make it easier to migrate to a differently named data source.
SQL that wants to generate XHTML output can use an new output parameter value of xhtml. The result will be rendered as XHTML before display.
Additional parameters to control table class, table style, and row styles. Unique row styles can be set for the heading rows, and any number of data rows. Row styles for data rows repeat when the number of data rows exceeds the number of row styles. This allows various kinds of stripping.
Helping administrators manage usage.
Helping administrators manage usage.
Affects sql macros created with the editor that reference an attachment or similar without any body content. See SQL-171. Does not affect wiki markup macros.
Native macros available in the Macro Browser. Confluence 3.x wiki macros are still supported.
Confluence 4.3 has storage space based templates. This incompatibility means that script support that gets text from a space template is broken since the returned content is now storage format. To accommodate this problem, change the handling of this data to look for unformated text in the template. Consider any content that is wrapped in a noformat or wiki-markup (CWP:Wiki Plugin for Confluence) as the plain content from the template. All other data in the template will be ignored.
The incompatibility requires templates that are used for this capability to be updated to surround the text with the noformat or wiki-markup macros. Most standard usage does not employ this technique, however some SQL users do use this extensively. To ease migration pains, support has been added for releases previous to Confluence 4.3 to allow the accommodation as well. In this case the noformat macro must be the first and last text in the template. This is supported by SQL plugin release 5.0.0 and later as well as 4.5.0 (for Confluence 3.5.x specifically).
Confluence 4.3 introduced some column sorting capability. This interferes with sql table support. Fortunately, Confluence developers provided a capability to disable this behavior for specific tables. This support is used for tables wrapped with sql, table-plus, csv, and similar macros supporting Common table capabilities
Likely the last release supporting Confluence 3.x. See Compatibility - Confluence.
This release is roughly equivalent to the 5.0.0 release except for Confuence 4.x specifics.
Note: Full Confluence 4.x native compatibility will be available in version 5.0 to be released in the near future.
Now an Atlassian paid plugin - see this announcement.
SQL-103 - XSS fixes
{jiraissues:url=http://developer.atlassian.com/jira/secure/IssueNavigator.jspa?view=rss&pid=10147&fixfor=11616&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none|columns=key,priority,summary,updated,asignee,reporter,status|renderMode=static}