Release Notes 8.5

Release Notes 8.4

Release Notes 8.3

Release Notes 8.2

Release Notes 8.1

Release Notes 8.0

Release Notes 8.0 (important!)

Release Notes 7.1

Release Notes 7.1

Release Notes 7.0

Release Notes 7.0

Release Notes 7.0

Release Notes 6.5

Release Notes 6.4

Release Notes 6.3

Release Notes 6.2

Release notes 6.1

Release notes 6.1

SQL-237: Excessive perm gen memory use when using profile defined data sources. Application server defined data sources do not have a problem.

sql-file=*ANY
sql-file.datasource.*=*ANY
sql-file.file.authorized.sql=*ANY

Date sorting improvements

1. A new date sorting option - column type M
2. Advanced date sorting bundled with plugin eliminating need for server install
3. International language support

See Advanced date sorting for more details.

sql-file=*ANY
sql-file.datasource.*=*ANY
sql-file.file.authorized.sql=*ANY

Date sorting improvements

1. A new date sorting option - column type M
2. Advanced date sorting bundled with plugin eliminating need for server install
3. International language support

See Advanced date sorting for more details.

Fix a dependency problem which may cause installs on Confluence 5.x to fail.

Improvements and Fixes

1. Fix a regression error that caused a display problem with horizontal row orientation.
2. Improve the look and usability of the configuration display especially on Confluence 4.x.
3. Improve macro security use by allowing user based page restrictions for a member of an authorized group.

This release fixes a security exposure for customer using Macro Security for Confluence to secure use of the sql macros.

Dynamic Data Sources

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.

Before and After SQL

Data source profiles can add before and after SQL that automatically gets inserted around the macro defined SQL.

Data Source Alias

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.

XHTML Output

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.

CSS parameters

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.

Improved logging - includes query timings

Helping administrators manage usage.

Query execution timeout

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.  

Confluence 4.x Native Macros

Native macros available in the Macro Browser. Confluence 3.x wiki macros are still supported.

Accommodate Confluence 4.3 Template Changes

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 Column Sorting

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.

1. Critical fix: SQL-163 - SQL tables not sorting. Needed for users running plugin version 4.3.0 and 4.3.1.
2. Other improvements

1. Allow output=unrenderedWiki for advanced use.
2. Update to latest level of common code.

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}