CData Cloud offers access to Backlog across several standard services and protocols, in a cloud-hosted solution. Any application that can connect to a MySQL or SQL Server database can connect to Backlog through CData Cloud.
CData Cloud allows you to standardize and configure connections to Backlog as though it were any other OData endpoint, or standard SQL Server/MySQL database.
This page provides a guide to Establishing a Connection to Backlog in CData Cloud, as well as information on the available resources, and a reference to the available connection properties.
Establishing a Connection shows how to authenticate to Backlog and configure any necessary connection properties to create a database in CData Cloud
Accessing data from Backlog through the available standard services and CData Cloud administration is documented in further details in the CData Cloud Documentation.
Connect to Backlog by selecting the corresponding icon in the Database tab. Required properties are listed under Settings. The Advanced tab lists connection properties that are not typically required.
Authentication methods available include APIKey and OAuth.
Set AuthScheme to APIToken.
To obtain the ApiKey:
Option 1: Obtain and Exchange a Verifier Code
To obtain a verifier code, you must authenticate at the OAuth authorization URL.
Follow the steps below to authenticate from the machine with an internet browser and obtain the OAuthVerifier connection property.
On the headless machine, set the following connection properties to obtain the OAuth authentication values:
After the OAuth settings file is generated, you need to re-set the following properties to connect:
Option 2: Transfer OAuth Settings
Prior to connecting on a headless machine, you need to create and install a connection with the driver on a device that supports an internet browser. Set the connection properties as described in "Desktop Applications" above.
After completing the instructions in "Desktop Applications", the resulting authentication values are encrypted and written to the location specified by OAuthSettingsLocation. The default filename is OAuthSettings.txt.
After you have successfully tested the connection, copy the OAuth settings file to your headless machine.
On the headless machine, set the following connection properties to connect to data:
By default, the Cloud attempts to negotiate SSL/TLS by checking the server's certificate against the system's trusted certificate store.
To specify another certificate, see the SSLServerCert property for the available formats to do so.
To connect through the Windows system proxy, you do not need to set any additional connection properties. To connect to other proxies, set ProxyAutoDetect to false.
In addition, to authenticate to an HTTP proxy, set ProxyAuthScheme, ProxyUser, and ProxyPassword, in addition to ProxyServer and ProxyPort.
Set the following properties:
This section shows the available API objects and provides more information on executing SQL to Backlog APIs.
Views describes the available views. Views are statically defined to model Teams, Users, TeamMembers, etc.
Tables describes the available tables. Tables are statically defined to model Projects, Issues, WikiPages, etc.
Stored Procedures are function-like interfaces to Backlog. Stored procedures allow you to execute operations to Backlog, including downloading documents and moving envelopes.
The Cloud models the data in Backlog as a list of tables in a relational database that can be queried using standard SQL statements.
Name | Description |
IssueAttachments | Returns data from issue attachments table. |
IssueComments | Returns data from issue comments table. |
IssueLinkedSharedFiles | Returns data from issue linked shared files table. |
Issues | Returns data from issues table. |
ProjectAdministrators | Returns data from project administrators table. |
ProjectCategories | Returns data from project categories table. |
ProjectCustomFieldItems | Returns data from project custom field items table. |
ProjectCustomFields | Returns data from project custom fields table. |
ProjectIssueTypes | Returns data from project issue types table. |
Projects | Returns data from projects table. |
ProjectStatuses | Returns data from project statuses table. |
ProjectTeams | Returns data from project teams table. |
ProjectUsers | Returns data from project users table. |
ProjectVersionMilestones | Returns data from project version milestones table. |
PullRequestAttachments | Returns data from pull request attachments table. |
PullRequestComments | Returns data from pull request comments table. |
PullRequests | Returns data from project pull requests table. |
Watchings | Returns data from watchings table. |
WikiPageAttachments | Gets list of files attached to Wiki. |
WikiPages | Returns data from wiki pages table. |
Returns data from issue attachments table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueAttachments WHERE IssueId = 6840954
INSERT is not supported for this table.
UPDATE is not supported for this table.
Delete can be executed by providing the IssueId AND ID.
DELETE FROM IssueAttachments WHERE IssueId = 6840954 AND Id = 3470553
Name | Type | ReadOnly | Description |
IssueId [KEY] | Int | False | |
Id [KEY] | Int | False | |
Name | String | False | |
Size | Int | False | |
Created | Datetime | False | |
CreatedById | Int | False | |
CreatedByUserId | String | False | |
CreatedByName | String | False | |
CreatedByKeyword | String | False | |
CreatedByRoleType | Int | False | |
CreatedByLanguage | String | False | |
CreatedByMailAddress | String | False | |
CreatedByNulabAccountName | String | False | |
CreatedByNulabId | String | False | |
CreatedByNulabAccountUniqueId | String | False |
Returns data from issue comments table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueComments WHERE IssueId = 6840954 SELECT * FROM IssueComments WHERE IssueId = 6840954 AND Id = 39040604
Insert can be executed by specifying the IssueId and Content.
INSERT INTO IssueComments (IssueId, Content) VALUES ('6840954', 'Sample Comment')
UPDATE IssueComments SET Content = 'Third' WHERE IssueId = 6840954 AND Id = 39042035"
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM IssueComments WHERE IssueId = 6840954 AND Id = 39042338
Name | Type | ReadOnly | Description |
IssueId [KEY] | Int | False | |
Id [KEY] | Int | False | |
Content | String | False | |
Created | Datetime | False | |
Updated | Datetime | False | |
CreatedById | Int | False | |
CreatedByUserId | String | False | |
CreatedByName | String | False | |
CreatedByRoleType | Int | False | |
CreatedByLanguage | String | False | |
CreatedByMailAddress | String | False | |
CreatedByNulabAccountName | String | False | |
CreatedByNulabId | String | False | |
CreatedByNulabAccountUniqueId | String | False |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description |
NotifiedUserId | String | |
AttachmentId | String |
Returns data from issues table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM Issues WHERE ID = 6840954 SELECT * FROM Issues WHERE ID IN (6840954, 6840954) SELECT * FROM Issues WHERE ProjectId = 112873 SELECT * FROM Issues WHERE ProjectId IN (112873, 6840954) SELECT * FROM Issues WHERE StatusId = 1 SELECT * FROM Issues WHERE StatusId IN (112873, 6840954) SELECT * FROM Issues WHERE ResolutionId = 0 SELECT * FROM Issues WHERE ResolutionId IN (0, 3)
Insert can be executed by specifying the ProjectId, Summary, PriorityId and IssueTypeId.
INSERT INTO Issues (ProjectId, Summary, PriorityId, IssueTypeId) VALUES (114706, 'Summary', 3, 530959)
UPDATE Issues SET Summary = 'UPDATED_KEY23', ParentIssueId = '6700745', Comment = 'test' WHERE Id = 6700474
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM Issues WHERE IssueId = 6840954 AND Id = 3470553
Name | Type | ReadOnly | Description |
Id [KEY] | Int | False | |
ProjectId | Int | False | |
IssueKey | String | False | |
KeyId | Int | False | |
ParentIssueId | Int | False | |
Summary | String | False | |
Description | String | False | |
CustomAttributes | String | False | |
StartDate | Date | False | |
DueDate | Date | False | |
ActualHours | Decimal | False | |
EstimatedHours | Decimal | False | |
Created | Datetime | False | |
CreatedByUserName | String | False | |
CreatedByUserId | String | False | |
Updated | Datetime | False | |
UpdatedByUserName | String | False | |
UpdatedByUserId | String | False | |
ResolutionId | Int | False | |
ResolutionName | String | False | |
PriorityId | Int | False | |
PriorityName | String | False | |
IssueTypeId | Int | False | |
IssueTypeName | String | False | |
IssueTypeProjectId | Int | False | |
IssueTypeColor | String | False | |
IssueTypeDisplayOrder | Int | False | |
StatusId | Int | False | |
StatusProjectId | Int | False | |
StatusName | String | False | |
StatusColor | String | False | |
StatusDisplayOrder | Int | False | |
AssigneeId | Int | False | |
AssigneeName | String | False | |
AssigneeRoleType | Int | False | |
AssigneeLanguage | String | False | |
AssigneeMailAddress | String | False |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description |
Category | String | |
Version | String | |
Milestone | String | |
ParentChild | Int |
The allowed values are 0, 1, 2, 3, 4. |
Attachment | Boolean | |
SharedFile | Boolean | |
CreatedSince | String | |
CreatedUntil | String | |
UpdatedSince | String | |
UpdatedUntil | String | |
StartDateSince | String | |
StartDateUntil | String | |
DueDateSince | String | |
DueDateUntil | String | |
Keyword | String | |
Comment | String |
Returns data from project administrators table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectAdministrators WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId and UserId.
INSERT INTO ProjectAdministrators (ProjectId, UserId) VALUES ('114706', '280728')
UPDATE is not supported for this table.
Delete can be executed by specifying the ProjectId AND UserId.
DELETE FROM ProjectAdministrators WHERE ProjectId = 114706 AND UserId = 280728
Name | Type | ReadOnly | Description |
ProjectId [KEY] | Int | False | |
UserId [KEY] | Int | False | |
UserCode | String | False | |
Name | String | False | |
Keyword | String | False | |
NulabAccountName | String | False | |
NulabId | String | False | |
NulabAccountUniqueId | String | False | |
RoleType | Int | False | |
Language | String | False | |
MailAddress | String | False |
Returns data from project categories table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectCategories WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId and Name.
INSERT INTO ProjectCategories (ProjectId, Name) VALUES ('114706', 'cat4')
UPDATE ProjectCategories SET Name = 'Sample' WHERE ProjectId = 114706 AND Id = 205625
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM ProjectCategories WHERE ProjectId = 114706 AND Id = 205622
Name | Type | ReadOnly | Description |
ProjectId [KEY] | Int | False | |
Id [KEY] | Int | False | |
Name | String | False | |
DisplayOrder | Int | False |
Returns data from project custom field items table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectCustomFieldItems WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId, CustomFieldId and Name.
INSERT INTO ProjectCustomFieldItems (ProjectId, CustomFieldId, Name) VALUES ('114706', '44072', 'Fourth')
UPDATE ProjectCustomFieldItems SET Name = 'Fourth4' WHERE ProjectId = 114706 AND CustomFieldId = 44072 AND ItemId = 4
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM ProjectCustomFieldItems WHERE ProjectId = 114706 AND CustomFieldId = 44072 AND ItemId = 5
Name | Type | ReadOnly | Description |
ProjectId [KEY] | Int | False | |
Id [KEY] | Int | False | |
DisplayOrder | String | True | |
Name | String | False | |
ItemId [KEY] | Int | False | |
ItemName | String | False | |
ItemDisplayOrder | String | True |
Returns data from project custom fields table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectCustomFields WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId, typeId and Name.
INSERT INTO ProjectCustomFields (ProjectId, Name, typeId) VALUES ('114706', 'Milestone4', 1)
UPDATE ProjectCustomFields SET Name = 'Third' WHERE ProjectId = 114706 AND Id = 44203
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM ProjectCustomFields WHERE ProjectId = 114706 AND Id = 44204
Name | Type | ReadOnly | Description |
ProjectId [KEY] | Int | False | |
Id [KEY] | Int | False | |
TypeId | String | False | |
Name | String | False | |
Description | String | False | |
Required | Booelan | False | |
AllowAddItem | Booelan | False | |
UseIssueType | Booelan | False | |
ApplicableIssueTypes | String | False | |
DisplayOrder | String | False |
Returns data from project issue types table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectIssueTypes WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId, Color and Name.
INSERT INTO ProjectIssueTypes (ProjectId, Name, Color) VALUES ('114706', 'Sample', '#ff9200')
UPDATE ProjectIssueTypes SET Name = 'ytryet43' WHERE ProjectId = 114706 AND Id = 532089
Name | Type | ReadOnly | Description |
ProjectId [KEY] | Int | False | |
Id [KEY] | Int | False | |
Name | String | False | |
Color | String | False | |
DisplayOrder | Int | True | |
TemplateSummary | String | False | |
TemplateDescription | String | False |
Returns data from projects table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM Projects WHERE Id = 114706 SELECT * FROM Projects WHERE ProjectKey = 'SAMPLE_KEY' SELECT * FROM Projects WHERE All = true SELECT * FROM Projects WHERE Archived = false
Insert can be executed by specifying the Name, ProjectKey, chartEnabled, projectLeaderCanEditProjectLeader, subtaskingEnabled, textFormattingRule, ProjectLeaderCanEditProjectLeader, UseDevAttributes and UseWikiTreeView.
INSERT INTO Projects (Name, ProjectKey, chartEnabled, projectLeaderCanEditProjectLeader, subtaskingEnabled, textFormattingRule, ProjectLeaderCanEditProjectLeader, UseDevAttributes, UseWikiTreeView) VALUES ('InsertedName', 'INSERTED_KEY_3', false, true, true, markdown, true, false, false)
UPDATE Projects SET ProjectKey = 'UPDATED_KEY2', Name = 'UpdatedName2' WHERE Id = 112873
Delete can be executed by specifying ID.
DELETE FROM Projects WHERE Id = 113332
Name | Type | ReadOnly | Description |
Id [KEY] | Int | False | |
ProjectKey | String | False | |
Name | String | False | |
DisplayOrder | Int | False | |
ChartEnabled | Boolean | False | |
SubtaskingEnabled | Boolean | False | |
ProjectLeaderCanEditProjectLeader | Boolean | False | |
UseDevAttributes | Boolean | False | |
UseWikiTreeView | Boolean | False | |
TextFormattingRule | String | False | |
Archived | Boolean | False | |
useResolvedForChart | Boolean | False | |
useWiki | Boolean | False | |
useFileSharing | Boolean | False | |
useOriginalImageSizeAtWiki | Boolean | False |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description |
All | Boolean |
Returns data from project statuses table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectStatuses WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId, Name and Color.
Possible values for Color column are #ea2c00 ,#e87758 ,#e07b9a ,#868cb7 ,#3b9dbd ,#4caf93 ,#b0be3c ,#eda62a ,#f42858, #393939.
INSERT INTO ProjectStatuses (ProjectId, Name, Color) VALUES ('117182', 'Sample', '#3b9dbd')
UPDATE ProjectStatuses SET Name = 'Sample', color = '#ea2c00' WHERE ProjectId = 114706 AND Id = 18504
Name | Type | ReadOnly | Description |
Id [KEY] | Int | False | |
ProjectId [KEY] | Int | False | |
Name | String | False | |
Color | String | False | |
DisplayOrder | Int | True |
Returns data from project teams table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectTeams WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId and TeamId.
INSERT INTO ProjectTeams (ProjectId, TeamId) VALUES ('114706', '55083')
UPDATE is not supported for this table.
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM ProjectTeams WHERE ProjectId = 114706 AND TeamId = 55082
Name | Type | ReadOnly | Description |
ProjectId [KEY] | Int | False | |
TeamId [KEY] | Int | False | |
Name | String | True | |
DisplayOrder | Int | True | |
Created | Datetime | True | |
CreatedById | Int | True | |
CreatedByUserId | String | True | |
CreatedByName | String | True | |
CreatedByRoleType | Int | True | |
CreatedByLang | String | True | |
CreatedByMailAddress | String | True | |
Updated | Datetime | True | |
UpdatedById | Int | True | |
UpdatedByUserId | String | True | |
UpdatedByName | String | True | |
UpdatedByRoleType | Int | True | |
UpdatedByLang | String | True | |
UpdatedByMailAddress | String | True |
Returns data from project users table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectUsers WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId and UserId.
INSERT INTO ProjectUsers (ProjectId, UserId) VALUES ('114706', '280728')
UPDATE is not supported for this table.
Delete can be executed by specifying the ProjectId AND UserId.
DELETE FROM ProjectUsers WHERE ProjectId = 114706 AND UserId = 280728
Name | Type | ReadOnly | Description |
ProjectId [KEY] | Int | False | |
UserId [KEY] | Int | False | |
UserCode | String | False | |
Name | String | False | |
Keyword | String | False | |
NulabAccountName | String | False | |
NulabId | String | False | |
NulabAccountUniqueId | String | False | |
RoleType | Int | False | |
Language | String | False | |
MailAddress | String | False |
Returns data from project version milestones table.
projectversionmilestones
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectVersionMilestones WHERE ProjectId = 114706
Insert can be executed by specifying the ProjectId and Name.
INSERT INTO ProjectVersionMilestones (ProjectId, Name) VALUES ('114706', 'Milestone4')
UPDATE ProjectVersionMilestones SET Name = 'Sample' WHERE ProjectId = 114706 AND Id = 138889
Delete can be executed by specifying the ProjectId AND ID.
DELETE FROM ProjectVersionMilestones WHERE ProjectId = 114706 AND Id = 138890
Name | Type | ReadOnly | Description |
ProjectId [KEY] | Int | False | |
Id [KEY] | Int | False | |
Name | String | False | |
Description | String | False | |
DisplayOrder | Int | True | |
StartDate | Date | False | |
ReleaseDueDate | Date | False | |
Archived | Boolean | True |
Returns data from pull request attachments table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId, RepositoryId and PullRequestNumber are required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM PullRequestAttachments WHERE ProjectId = '94706' AND RepositoryId = 21949 AND PullRequestNumber = 2
INSERT is not supported for this table.
UPDATE is not supported for this table.
Delete can be executed by specifying the ProjectId, RepositoryId, PullRequestNumber AND ID.
DELETE FROM PullRequestAttachments WHERE ProjectId = 39470 AND RepositoryId = 21949 AND PullRequestNumber = 2 AND ID = 3
Name | Type | ReadOnly | Description |
ProjectId [KEY] | Int | True | |
RepositoryId [KEY] | Int | True | |
PullRequestNumber [KEY] | Int | True | |
Id [KEY] | Int | True | |
Name | String | True | |
Size | Int | True | |
Created | Datetime | True | |
CreatedById | Int | True | |
CreatedByUserId | String | True | |
CreatedByName | String | True | |
CreatedByKeyword | String | True | |
CreatedByRoleType | Int | True | |
CreatedByLanguage | String | True | |
CreatedByMailAddress | String | True | |
CreatedByNulabAccountName | String | True | |
CreatedByNulabId | String | True | |
CreatedByNulabAccountUniqueId | String | True |
Returns data from pull request comments table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId, RepositoryId and PullRequestNumber are required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM PullRequestComments WHERE ProjectId = 114706 AND RepositoryId = 22462 AND PullRequestNumber = 2
Insert can be executed by specifying the ProjectId, RepositoryId, PullRequestNumber and Content.
INSERT INTO PullRequestComments (ProjectId, RepositoryId, PullRequestNumber, Content) VALUES ('114706', '22462', '2', 'FirstComment')
UPDATE PullRequestComments SET Content = 'Third' WHERE ProjectId = 114706 AND RepositoryId = 22462 AND PullRequestNumber = 2 AND ID = 3
Delete is not supported for this table.
Name | Type | ReadOnly | Description |
ProjectId | Int | False | |
RepositoryId | Int | False | |
PullRequestNumber | Int | False | |
Id [KEY] | Int | False | |
Content | String | False | |
Created | Datetime | True | |
Updated | Datetime | True | |
CreatedById | Int | True | |
CreatedByUserId | String | True | |
CreatedByName | String | True | |
CreatedByRoleType | Int | True | |
CreatedByLanguage | String | True | |
CreatedByMailAddress | String | True | |
CreatedByNulabAccountName | String | True | |
CreatedByNulabId | String | True | |
CreatedByNulabAccountUniqueId | String | True |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description |
NotifiedUserId | String |
Returns data from project pull requests table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId and RepositoryId are required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM PullRequests WHERE ProjectId = '114706' AND RepositoryId = 22462" SELECT * FROM PullRequests WHERE ProjectId = '114706' AND RepositoryId = 22462 AND Number = 2
Insert can be executed by specifying the ProjectId, RepositoryId, Summary, description, base and branch.
INSERT INTO PullRequests (ProjectId, RepositoryId, Summary, description, base, branch) VALUES ('114706', '22462', 'First', 'FirstPullReq', 'main', 'sample')
UPDATE PullRequests SET Summary = 'Third' WHERE ProjectId = 114706 AND RepositoryId = 22462 AND Number = 44203
Delete is not supported for this table.
Name | Type | ReadOnly | Description |
ProjectId [KEY] | Int | False | |
RepositoryId [KEY] | Int | False | |
Id [KEY] | Int | False | |
Number | Int | False | |
Summary | String | False | |
Description | String | False | |
Base | String | False | |
Branch | String | False | |
BaseCommit | String | True | |
BranchCommit | String | True | |
CloseAt | Datetime | True | |
MergeAt | Datetime | True | |
StatusId | Int | True | |
StatusName | String | True | |
IssueId | Int | False | |
AssigneeId | Int | False | |
AssigneeName | String | True | |
AssigneeRoleType | Int | True | |
AssigneeLanguage | String | True | |
AssigneeMailAddress | String | True | |
Created | Datetime | True | |
CreatedById | Int | True | |
CreatedByUserId | String | True | |
CreatedByName | String | True | |
CreatedByKeyword | String | True | |
CreatedByRoleType | Int | True | |
CreatedByLanguage | String | True | |
CreatedByMailAddress | String | True | |
CreatedByNulabAccountName | String | True | |
CreatedByNulabId | String | True | |
CreatedByNulabAccountUniqueId | String | True | |
Updated | Datetime | True | |
UpdatedById | Int | True | |
UpdatedByUserId | String | True | |
UpdatedByName | String | True | |
UpdatedByKeyword | String | True | |
UpdatedByRoleType | Int | True | |
UpdatedByLanguage | String | True | |
UpdatedByMailAddress | String | True | |
UpdatedByNulabAccountName | String | True | |
UpdatedByNulabId | String | True | |
UpdatedByNulabAccountUniqueId | String | True |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description |
NotifiedUserId | String | |
AttachmentId | String |
Returns data from watchings table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The UserId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM Watchings WHERE UserId = '280688' SELECT * FROM Watchings WHERE Id = '145169'
Insert can be executed by specifying the IssueId and Note.
INSERT INTO Watchings (IssueId, Note) VALUES ('6868643', 'Sample')
UPDATE Watchings SET Note = 'Third' WHERE Id = 145171
Delete can be executed by specifying ID.
DELETE FROM Watchings WHERE Id = 145170
Name | Type | ReadOnly | Description |
UserId | Int | False | |
Id [KEY] | Int | False | |
Note | String | False | |
Type | String | True | |
IssueId | String | True | |
ResourceAlreadyRead | Boolean | True | |
LastContentUpdated | Datetime | True | |
Created | Datetime | True | |
Updated | Datetime | True |
Gets list of files attached to Wiki.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The WikiPageId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM WikiPageAttachments WHERE WikiPageId = '639459'
INSERT is not supported for this table.
UPDATE is not supported for this table.
Delete can be executed by specifying the IssueId AND ID.
DELETE FROM WikiPageAttachments WHERE WikiPageId = 639459 AND Id = 188522
Name | Type | ReadOnly | Description |
WikiPageId [KEY] | Int | False | |
Id [KEY] | Int | False | |
Name | String | False | |
Size | Int | False | |
Created | Datetime | False | |
CreatedById | Int | False | |
CreatedByUserId | String | False | |
CreatedByName | String | False | |
CreatedByKeyword | String | False | |
CreatedByRoleType | Int | False | |
CreatedByLanguage | String | False | |
CreatedByMailAddress | String | False | |
CreatedByNulabAccountName | String | False | |
CreatedByNulabId | String | False | |
CreatedByNulabAccountUniqueId | String | False |
Returns data from wiki pages table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM WikiPages WHERE ProjectId = '114706' SELECT * FROM WikiPages WHERE Id = 639460
Insert can be executed by specifying the ProjectId, Content and Name.
INSERT INTO WikiPages (ProjectId, Name, Content) VALUES ('114706', 'FirstWiki3', 'Sample Comment')
UPDATE WikiPages SET Name = 'UPDATED', Content = 'UPDATED' WHERE Id = 639460
Delete can be executed by specifying ID.
DELETE FROM WikiPages WHERE Id = 639461
Name | Type | ReadOnly | Description |
ProjectId | Int | False | |
Id [KEY] | Int | False | |
Name | String | False | |
Content | String | False | |
Created | Datetime | True | |
CreatedById | Int | True | |
CreatedByUserId | String | True | |
CreatedByName | String | True | |
CreatedByKeyword | String | True | |
CreatedByRoleType | Int | True | |
CreatedByLanguage | String | True | |
CreatedByMailAddress | String | True | |
CreatedByNulabAccountName | String | True | |
CreatedByNulabId | String | True | |
CreatedByNulabAccountUniqueId | String | True | |
Updated | Datetime | True | |
UpdatedById | Int | True | |
UpdatedByUserId | String | True | |
UpdatedByName | String | True | |
UpdatedByKeyword | String | True | |
UpdatedByRoleType | Int | True | |
UpdatedByLanguage | String | True | |
UpdatedByMailAddress | String | True | |
UpdatedByNulabAccountName | String | True | |
UpdatedByNulabId | String | True | |
UpdatedByNulabAccountUniqueId | String | True |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description |
MailNotify | Boolean |
Views are similar to tables in the way that data is represented; however, views are read-only.
Queries can be executed against a view as if it were a normal table.
Name | Description |
IssueCategories | Returns data from issue categories table. |
IssueCommentChangeLog | Returns data from issue comment change log table. |
IssueCommentNotifications | Returns data from issue comment notifications table. |
IssueCommentStars | Returns data from issue comment starts table. |
IssueMilestones | Returns data from issue milestones table. |
IssueParticipants | Returns list of participants of an issue. |
IssueVersions | Returns data from issue versions table. |
Licenses | Returns licence. |
Notifications | Returns own notifications. |
Priorities | Returns data from priorities table. |
ProjectRecentUpdates | Returns recent update in the project. |
ProjectSharedFiles | Gets list of Project Shared Files |
ProjectTeamMembers | Returns data from project team members table. |
PullRequestCommentChangeLog | Returns data from pull request comment changelog table. |
PullRequestCommentNotifications | Returns data from pull request comment notifications table. |
PullRequestCommentStars | Returns data from pull request comment starts table. |
Repositories | Returns data from project repositories table. |
Resolutions | Returns data from resolutions table. |
Space | Returns information about your space. |
SpaceDiskUsage | Returns information about space disk usage. |
SpaceDiskUsageDetails | Returns information about space disk details usage. |
SpaceNotifications | Returns space notification. |
SpaceUpdates | Returns recent updates in your space. |
TeamMembers | Returns data from team members table. |
Teams | Returns data from teams table. |
UserReceivedStars | Returns the list of stars that user received. |
UserRecentlyViewedIssues | Returns list of issues which the user viewed recently. |
UserRecentlyViewedProjects | Returns list of projects which the user viewed recently. |
UserRecentlyViewedWikiPages | Returns list of Wikis which the user viewed recently. |
UserRecentUpdates | Returns user recent updates. |
Users | Returns data from users table. |
WikiPageHistory | Returns history of Wiki page. |
WikiPageLinkedSharedFiles | Returns data from wiki page linked shred files table. |
WikiPageStars | Returns list of stars received on the Wiki page. |
WikiPageTags | Returns list of tags that are used in the project. |
Returns data from issue categories table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueCategories WHERE IssueId = 6840954
Name | Type | Description |
IssueId | String | |
Id [KEY] | Int | |
Name | String | |
DisplayOrder | String |
Returns data from issue comment change log table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueCommentChangeLog WHERE IssueId = 6840954
Name | Type | Description |
IssueId | Int | |
CommentId | Int | |
AttachmentInfo | String | |
AttributeInfo | String | |
Field | String | |
NewValue | String | |
NotificationInfo | String | |
OriginalValue | String |
Returns data from issue comment notifications table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueCommentNotifications WHERE IssueId = 6840954
Name | Type | Description |
IssueId | Int | |
CommentId | Int | |
NotificationId [KEY] | Int | |
Reason | String | |
AlreadyRead | Boolean | |
ResourceAlreadyRead | Boolean | |
CreatedById | Int | |
CreatedByUserId | String | |
CreatedByName | String | |
CreatedByKeyword | String | |
CreatedByRoleType | Int | |
CreatedByLanguage | String | |
CreatedByMailAddress | String | |
CreatedByNulabAccountName | String | |
CreatedByNulabId | String | |
CreatedByNulabAccountUniqueId | String |
Returns data from issue comment starts table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueCommentStars WHERE IssueId = 6840954
Name | Type | Description |
IssueId | Int | |
CommentId | Int | |
StarId [KEY] | Int | |
Comment | String | |
Title | String | |
Url | String | |
Created | Datetime | |
PresenterId | Int | |
PresenterUserId | String | |
PresenterName | String | |
PresenterKeyword | String | |
PresenterRoleType | Int | |
PresenterLanguage | String | |
PresenterMailAddress | String | |
PresenterNulabAccountName | String | |
PresenterNulabId | String | |
PresenterNulabAccountUniqueId | String |
Returns data from issue milestones table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueMilestones WHERE IssueId = 6868745
Name | Type | Description |
IssueId | String | |
Id [KEY] | Int | |
Name | String | |
Description | String | |
Archived | Boolean | |
ProjectId | Int | |
ReleaseDueDate | Date | |
StartDate | Date | |
DisplayOrder | String |
Returns list of participants of an issue.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueParticipants WHERE IssueId = '6840954'
Name | Type | Description |
IssueId | Int | |
Id [KEY] | Int | |
UserId | String | |
Name | String | |
Keyword | String | |
NulabAccountName | String | |
NulabId | String | |
NulabAccountUniqueId | String | |
RoleType | Int | |
Language | String | |
MailAddress | String |
Returns data from issue versions table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The IssueId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM IssueVersions WHERE IssueId = 6868745
Name | Type | Description |
IssueId | String | |
Id [KEY] | Int | |
Name | String | |
Description | String | |
Archived | Boolean | |
ProjectId | Int | |
ReleaseDueDate | Date | |
StartDate | Date | |
DisplayOrder | String |
Returns licence.
Backlog does not support any column for filtering this table. All filters will be executed client side.
Name | Type | Description |
Active | Boolean | |
AttachmentLimit | Int | |
AttachmentLimitPerFile | Int | |
AttachmentNumLimit | Int | |
Attribute | Boolean | |
AttributeLimit | Int | |
Burndown | Boolean | |
CommentLimit | Int | |
ComponentLimit | Int | |
FileSharing | Boolean | |
Gantt | Boolean | |
Git | Boolean | |
IssueLimit | Int | |
LicenceTypeId | Int | |
LimitDate | Date | |
NulabAccount | Boolean | |
ParentChildIssue | Boolean | |
PostIssueByMail | Boolean | |
ProjectGroup | Boolean | |
ProjectLimit | Int | |
PullRequestAttachmentLimitPerFile | Int | |
PullRequestAttachmentNumLimit | Int | |
RemoteAddress | Boolean | |
RemoteAddressLimit | Int | |
StartedOn | Datetime | |
StorageLimit | Int | |
Subversion | Boolean | |
SubversionExternal | Boolean | |
UserLimit | Int | |
VersionLimit | Int | |
WikiAttachment | Boolean | |
WikiAttachmentLimitPerFile | Int | |
WikiAttachmentNumLimit | Int |
Returns own notifications.
Backlog does not support any column for filtering this table. All filters will be executed client side.
Name | Type | Description |
Id [KEY] | Int | |
AlreadyRead | Boolean | |
Reason | Int | |
ResourceAlreadyRead | Int | |
Created | Int | |
ProjectId | Int | |
ProjectKey | String | |
ProjectName | String | |
ProjectDisplayOrder | Int | |
ProjectChartEnabled | Boolean | |
ProjectSubtaskingEnabled | Boolean | |
ProjectProjectLeaderCanEditProjectLeader | Boolean | |
ProjectUseDevAttributes | Boolean | |
ProjectUseWikiTreeView | Boolean | |
ProjectTextFormattingRule | String | |
ProjectArchived | Boolean | |
IssueId | Int | |
IssueProjectId | Int | |
IssueKey | String | |
IssueKeyId | Int | |
IssueTypeId | Int | |
IssueTypeName | String | |
IssueTypeColor | String | |
IssueTypeProjectId | Int | |
IssueTypeDisplayOrder | Int | |
IssueSummary | String | |
IssueDescription | String | |
IssueResolutions | String | |
IssuePriorityId | Int | |
IssuePriorityName | String | |
IssueStatusId | Int | |
IssueStatusName | String | |
IssueStatusColor | String | |
IssueStatusProjectId | Int | |
IssueStatusDisplayOrder | Int | |
IssueAssigneeId | Int | |
IssueAssigneeName | String | |
IssueAssigneeRoleType | Int | |
IssueAssigneeLanguage | String | |
IssueAssigneeMailAddress | String | |
IssueCategories | String | |
IssueVersions | String | |
IssueMilestones | String | |
IssueCustomFields | String | |
IssueAttachments | String | |
IssueSharedFiles | String | |
IssueStars | String | |
IssueStartDate | Date | |
IssueDueDate | Date | |
IssueEstimatedHours | Decimal | |
IssueActualHours | Decimal | |
IssueParentIssueId | Int | |
IssueCreated | Datetime | |
IssueCreatedById | Int | |
IssueCreatedByUserId | String | |
IssueCreatedByName | String | |
IssueCreatedByKeyword | String | |
IssueCreatedByNulabAccountName | String | |
IssueCreatedByNulabId | String | |
IssueCreatedByNulabAccountUniqueId | String | |
IssueCreatedByRoleType | Int | |
IssueCreatedByLanguage | String | |
IssueCreatedByMailAddress | String | |
IssueUpdated | Datetime | |
IssueUpdatedById | Int | |
IssueUpdatedByUserId | String | |
IssueUpdatedByName | String | |
IssueUpdatedByKeyword | String | |
IssueUpdatedByNulabAccountName | String | |
IssueUpdatedByNulabId | String | |
IssueUpdatedByNulabAccountUniqueId | String | |
IssueUpdatedByRoleType | Int | |
IssueUpdatedByLanguage | String | |
IssueUpdatedByMailAddress | String | |
CommentId | Int | |
CommentContent | String | |
CommentCreated | String | |
SentById | Int | |
SentByUserId | String | |
SentByName | String | |
SentByKeyword | String | |
SentByNulabAccountName | String | |
SentByNulabId | String | |
SentByNulabAccountUniqueId | String | |
SentByRoleType | Int | |
SentByLanguage | String | |
SentByMailAddress | String |
Returns data from priorities table.
Backlog does not support any column for filtering this table. All filters will be executed client side.
Name | Type | Description |
Id [KEY] | Int | |
Name | String |
Returns recent update in the project.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectRecentUpdates WHERE ProjectId = 114706
Name | Type | Description |
Id [KEY] | Int | |
Created | Datetime | |
Type | String | |
ContentId | Int | |
Content | String | |
ContentDiff | String | |
ContentKeyId | String | |
ContentDescription | String | |
ContentSummary | String | |
ContentRepository | String | |
ContentAttachments | String | |
ContentSharedFiles | String | |
ContentComments | String | |
ContentChanges | String | |
ContentParties | String | |
ProjectId | Int | |
ProjectKey | String | |
ProjectName | String | |
ProjectDisplayOrder | Int | |
ProjectChartEnabled | Boolean | |
ProjectSubtaskingEnabled | Boolean | |
ProjectProjectLeaderCanEditProjectLeader | Boolean | |
ProjectUseDevAttributes | Boolean | |
ProjectUseWikiTreeView | Boolean | |
ProjectTextFormattingRule | String | |
ProjectArchived | Boolean | |
CreatedById | Int | |
CreatedByUserId | String | |
CreatedByName | String | |
CreatedByKeyword | String | |
CreatedByNulabAccountName | String | |
CreatedByNulabId | String | |
CreatedByNulabAccountUniqueId | String | |
CreatedByRoleType | Int | |
CreatedByLanguage | String | |
CreatedByMailAddress | String |
Returns data from project team members table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM ProjectTeamMembers WHERE ProjectId = 114706
Name | Type | Description |
ProjectId | Int | |
TeamId | Int | |
MemberId | Int | |
UserId | String | |
Name | String | |
Keyword | String | |
NulabAccountName | String | |
NulabId | String | |
NulabAccountUniqueId | String | |
RoleType | Int | |
Lang | String | |
MailAddress | String |
Returns data from pull request comment changelog table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId, RepositoryId and PullRequestNumber are required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM PullRequestCommentChangeLog WHERE ProjectId = '114706' AND RepositoryId = 22462 AND PullRequestNumber = 2
Name | Type | Description |
ProjectId | Int | |
RepositoryId | Int | |
PullRequestNumber | Int | |
AttachmentInfo | String | |
AttributeInfo | String | |
Field | String | |
NewValue | String | |
NotificationInfo | String | |
OriginalValue | String |
Returns data from pull request comment notifications table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId, RepositoryId and PullRequestNumber are required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM PullRequestCommentNotifications WHERE ProjectId = '114706' AND RepositoryId = 22462 AND PullRequestNumber = 2
Name | Type | Description |
ProjectId | Int | |
RepositoryId | Int | |
PullRequestNumber | Int | |
NotificationId [KEY] | Int | |
Reason | String | |
AlreadyRead | Boolean | |
ResourceAlreadyRead | Boolean | |
CreatedById | Int | |
CreatedByUserId | String | |
CreatedByName | String | |
CreatedByKeyword | String | |
CreatedByRoleType | Int | |
CreatedByLanguage | String | |
CreatedByMailAddress | String | |
CreatedByNulabAccountName | String | |
CreatedByNulabId | String | |
CreatedByNulabAccountUniqueId | String |
Returns data from pull request comment starts table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId, RepositoryId and PullRequestNumber are required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM PullRequestCommentStars WHERE ProjectId = '114706' AND RepositoryId = 22462 AND PullRequestNumber = 2
Name | Type | Description |
ProjectId | Int | |
RepositoryId | Int | |
PullRequestNumber | Int | |
StarId [KEY] | Int | |
Comment | String | |
Title | String | |
Url | String | |
Created | Datetime | |
PresenterId | Int | |
PresenterUserId | String | |
PresenterName | String | |
PresenterKeyword | String | |
PresenterRoleType | Int | |
PresenterLanguage | String | |
PresenterMailAddress | String | |
PresenterNulabAccountName | String | |
PresenterNulabId | String | |
PresenterNulabAccountUniqueId | String |
Returns data from project repositories table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM Repositories WHERE ProjectId = 117182 SELECT * FROM Repositories WHERE ProjectId = 117182 AND Id = 22862 SELECT * FROM Repositories WHERE ProjectId = 117182 AND Name = 'First'
Name | Type | Description |
Id [KEY] | Int | |
ProjectId | Int | |
Name | String | |
Description | String | |
HookUrl | String | |
HttpUrl | String | |
SshUrl | String | |
DisplayOrder | Int | |
PushedAt | Datetime | |
Created | Datetime | |
CreatedById | Int | |
CreatedByUserId | String | |
CreatedByName | String | |
CreatedByKeyword | String | |
CreatedByRoleType | Int | |
CreatedByLanguage | String | |
CreatedByMailAddress | String | |
CreatedByNulabAccountName | String | |
CreatedByNulabId | String | |
CreatedByNulabAccountUniqueId | String | |
Updated | Datetime | |
UpdatedById | Int | |
UpdatedByUserId | String | |
UpdatedByName | String | |
UpdatedByKeyword | String | |
UpdatedByRoleType | Int | |
UpdatedByLanguage | String | |
UpdatedByMailAddress | String | |
UpdatedByNulabAccountName | String | |
UpdatedByNulabId | String | |
UpdatedByNulabAccountUniqueId | String |
Returns data from resolutions table.
Backlog does not support any column for filtering this table. All filters will be executed client side.
Name | Type | Description |
Id [KEY] | Int | |
Name | String |
Returns information about your space.
Backlog does not support any column for filtering this table. All filters will be executed client side.
Name | Type | Description |
SpaceKey | String | |
Name | String | |
OwnerId [KEY] | Int | |
Language | String | |
Timezone | String | |
ReportSendTime | Hour | |
TextFormattingRule | String | |
Created | Datetime | |
Updated | Datetime |
Returns information about space disk usage.
Backlog does not support any column for filtering this table. All filters will be executed client side.
Name | Type | Description |
Capacity | String | |
Issue | String | |
Wiki | String | |
File | Int | |
Subversion | Int | |
Git | Int | |
GitLFS | Int | |
PullRequest | Int |
Returns information about space disk details usage.
Backlog does not support any column for filtering this table. All filters will be executed client side.
Name | Type | Description |
ProjectId | String | |
File | Int | |
Git | Int | |
GitLFS | Int | |
Issue | String | |
Wiki | String | |
Subversion | Int |
Returns space notification.
Backlog does not support any column for filtering this table. All filters will be executed client side.
Name | Type | Description |
Content | String | |
Updated | Datetime |
Returns recent updates in your space.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM SpaceUpdates WHERE Type = 13 SELECT * FROM SpaceUpdates WHERE Type IN (13, 5)
Name | Type | Description |
Id [KEY] | Int | |
Created | Datetime | |
Type | String | |
ContentId | Int | |
Content | String | |
ContentDiff | String | |
ContentKeyId | String | |
ContentDescription | String | |
ContentSummary | String | |
ContentRepository | String | |
ContentAttachments | String | |
ContentSharedFiles | String | |
ContentComments | String | |
ContentChanges | String | |
ContentParties | String | |
ProjectId | Int | |
ProjectKey | String | |
ProjectName | String | |
ProjectDisplayOrder | Int | |
ProjectChartEnabled | Boolean | |
ProjectSubtaskingEnabled | Boolean | |
ProjectProjectLeaderCanEditProjectLeader | Boolean | |
ProjectUseDevAttributes | Boolean | |
ProjectUseWikiTreeView | Boolean | |
ProjectTextFormattingRule | String | |
ProjectArchived | Boolean | |
CreatedById | Int | |
CreatedByUserId | String | |
CreatedByName | String | |
CreatedByKeyword | String | |
CreatedByNulabAccountName | String | |
CreatedByNulabId | String | |
CreatedByNulabAccountUniqueId | String | |
CreatedByRoleType | Int | |
CreatedByLanguage | String | |
CreatedByMailAddress | String |
Returns data from team members table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The TeamId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM TeamMembers WHERE TeamId = 54836
Name | Type | Description |
TeamId | Int | |
Id [KEY] | Int | |
UserId | String | |
Name | String | |
Keyword | String | |
NulabAccountName | String | |
NulabId | String | |
NulabAccountUniqueId | String | |
RoleType | Int | |
Lang | String | |
MailAddress | String |
Returns data from teams table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM Teams WHERE Id = 55081
Name | Type | Description |
Id [KEY] | Int | |
Name | String | |
DisplayOrder | Int | |
Members | String | |
Created | Datetime | |
CreatedById | Int | |
CreatedByUserId | String | |
CreatedByName | String | |
CreatedByRoleType | Int | |
CreatedByLang | String | |
CreatedByMailAddress | String | |
Updated | Datetime | |
UpdatedById | Int | |
UpdatedByUserId | String | |
UpdatedByName | String | |
UpdatedByRoleType | Int | |
UpdatedByLang | String | |
UpdatedByMailAddress | String |
Returns the list of stars that user received.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The UserId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM UserReceivedStars WHERE UserId = 263366
Name | Type | Description |
UserId | String | |
Id [KEY] | Int | |
Comment | String | |
Title | String | |
Url | String | |
Created | Datetime | |
PresenterId | Int | |
PresenterUserId | String | |
PresenterName | String | |
PresenterKeyword | String | |
PresenterRoleType | Int | |
PresenterLanguage | String | |
PresenterMailAddress | String | |
PresenterNulabAccountName | String | |
PresenterNulabId | String | |
PresenterNulabAccountUniqueId | String |
Returns list of issues which the user viewed recently.
Backlog does not support any column for filtering this table. All filters will be executed client side.
Name | Type | Description |
Id [KEY] | Int | |
ProjectId | Int | |
IssueKey | String | |
KeyId | Int | |
ParentIssueId | Int | |
Summary | String | |
Description | String | |
StartDate | Date | |
DueDate | Date | |
ActualHours | Decimal | |
EstimatedHours | Decimal |
Returns list of projects which the user viewed recently.
Backlog does not support any column for filtering this table. All filters will be executed client side.
Name | Type | Description |
Id [KEY] | Int | |
ProjectKey | String | |
Name | String | |
DisplayOrder | Int | |
ChartEnabled | Boolean | |
SubtaskingEnabled | Boolean | |
ProjectLeaderCanEditProjectLeader | Boolean | |
UseDevAttributes | Boolean | |
UseWikiTreeView | Boolean | |
TextFormattingRule | String | |
Archived | Boolean |
Returns list of Wikis which the user viewed recently.
Backlog does not support any column for filtering this table. All filters will be executed client side.
Name | Type | Description |
ProjectId | Int | |
Id [KEY] | Int | |
Name | String | |
Content | String | |
Created | Datetime |
Returns user recent updates.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The UserId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM UserRecentUpdates WHERE UserId = 263366 SELECT * FROM UserRecentUpdates WHERE UserId = 263366 AND Type = 3 SELECT * FROM UserRecentUpdates WHERE UserId = 263366 AND Type IN (3, 5)
Name | Type | Description |
UserId | String | |
Id [KEY] | Int | |
Created | Datetime | |
Type | String | |
ContentId | Int | |
Content | String | |
ContentDiff | String | |
ContentKeyId | String | |
ContentDescription | String | |
ContentSummary | String | |
ContentRepository | String | |
ContentAttachments | String | |
ContentSharedFiles | String | |
ContentComments | String | |
ContentChanges | String | |
ContentParties | String | |
ProjectId | Int | |
ProjectKey | String | |
ProjectName | String | |
ProjectDisplayOrder | Int | |
ProjectChartEnabled | Boolean | |
ProjectSubtaskingEnabled | Boolean | |
ProjectProjectLeaderCanEditProjectLeader | Boolean | |
ProjectUseDevAttributes | Boolean | |
ProjectUseWikiTreeView | Boolean | |
ProjectTextFormattingRule | String | |
ProjectArchived | Boolean | |
CreatedById | Int | |
CreatedByUserId | String | |
CreatedByName | String | |
CreatedByKeyword | String | |
CreatedByNulabAccountName | String | |
CreatedByNulabId | String | |
CreatedByNulabAccountUniqueId | String | |
CreatedByRoleType | Int | |
CreatedByLanguage | String | |
CreatedByMailAddress | String |
Returns data from users table.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM Users WHERE Id = 54836
Name | Type | Description |
Id [KEY] | Int | |
UserId | String | |
Name | String | |
NulabAccountName | String | |
NulabAccountID | String | |
NulabAccountUniqueId | String | |
RoleType | Int | |
Lang | String | |
MailAddress | String |
Returns history of Wiki page.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The WikiPageId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM WikiPageHistory WHERE WikiPageId = '639459'
Name | Type | Description |
WikiPageId | Int | |
PageId [KEY] | Int | |
Name | String | |
Content | String | |
Version | Int | |
Created | Datetime | |
CreatedById | Int | |
CreatedByUserId | String | |
CreatedByName | String | |
CreatedByKeyword | String | |
CreatedByRoleType | Int | |
CreatedByLanguage | String | |
CreatedByMailAddress | String | |
CreatedByNulabAccountName | String | |
CreatedByNulabId | String | |
CreatedByNulabAccountUniqueId | String |
Returns list of stars received on the Wiki page.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The WikiPageId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM WikiPageStars WHERE WikiPageId = '528251'
Name | Type | Description |
WikiPageId | Int | |
CommentId | Int | |
StarId [KEY] | Int | |
Comment | String | |
Title | String | |
Url | String | |
Created | Datetime | |
PresenterId | Int | |
PresenterUserId | String | |
PresenterName | String | |
PresenterKeyword | String | |
PresenterRoleType | Int | |
PresenterLanguage | String | |
PresenterMailAddress | String | |
PresenterNulabAccountName | String | |
PresenterNulabId | String | |
PresenterNulabAccountUniqueId | String |
Returns list of tags that are used in the project.
The Cloud will use the Backlog API to process WHERE clause conditions built with the following column and operator. The ProjectId is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following query is processed server side:
SELECT * FROM WikiPageTags WHERE ProjectId = '94706'
Name | Type | Description |
ProjectId | Int | |
Id [KEY] | Int | |
Name | String |
Stored procedures are function-like interfaces that extend the functionality of the Cloud beyond simple SELECT/INSERT/UPDATE/DELETE operations with Backlog.
Stored procedures accept a list of parameters, perform their intended function, and then return any relevant response data from Backlog, along with an indication of whether the procedure succeeded or failed.
Name | Description |
AddStar | Adds star. |
AttachFileToWiki | Attaches file to Wiki. |
LinkSharedFilesToWiki | Links Shared Files to Wiki. |
MarkWatchingAsRead | Mark a watching as read. |
PostAttachmentFile | Posts an attachment file for issue or wiki. |
RemoveProjectIssueType | Delete the Project Issue Type. |
RemoveProjectStatus | Delete the Project Status. |
RemoveSharedFileFromWiki | Removes link to shared file from Wiki. |
UpdatePullRequestCommentInformation | Updates pull request comment information.Authenticated user can update his own comments. |
UpdateSpaceNotification | Updates space notification. |
Adds star.
Name | Type | Required | Description |
IssueId | String | False | Id of the issue. |
CommentId | String | False | Id of the comment. |
WikiId | String | False | Id of the wiki. |
PullRequestId | String | False | Id of the pullRequest. |
PullRequestCommentId | String | False | Id of the pullRequestComment. |
Name | Type | Description |
Success | String | Returns True if procedure succeeded. |
Attaches file to Wiki.
Name | Type | Required | Description |
WikiId | String | True | Id of the issue. |
AttachmentId | String | True | Id of the attachment. You can specify multiple ids separating them by comma ','. |
Name | Type | Description |
Success | String | Returns True if the attachment succeeded. |
Mark a watching as read.
Name | Type | Required | Description |
WatchingId | String | True | Id of the watching. |
Name | Type | Description |
Success | String | Returns True if procedure succeeded. |
Posts an attachment file for issue or wiki.
Name | Type | Required | Description |
FileLocation | String | True | Location of the downloaded file. EX: C:\Temp\downloads\file.txt |
Name | Type | Description |
Success | String | Returns True if the upload succeeded. |
Delete the Project Issue Type.
Backlog allows only a small subset of columns to be used in the Exec query. These columns can typically be used with only = comparison.
For example:
EXECUTE RemoveProjectIssueType ProjectId ='123844', Id = '530228', SubstituteIssueTypeId = '530140'
Name | Type | Required | Description |
ProjectId | String | True | ProjectId. |
Id | String | True | Project Issue Type Id. |
SubstituteIssueTypeId | String | True | Project Issue Type Id to change linked issue. |
Name | Type | Description |
Success | String | Returns true if procedure succeeded. |
Delete the Project Status.
Backlog allows only a small subset of columns to be used in the Exec query. These columns can typically be used with only = comparison.
For example:
EXECUTE RemoveProjectStatus ProjectId ='123844', Id = '4', SubstituteStatusId = '3'
Name | Type | Required | Description |
ProjectId | String | True | ProjectId. |
Id | String | True | Project Status Id. |
SubstituteStatusId | String | True | Project Status Id to replace linked issues statuses. Issues which status are set to the deleted status will be set to the specied substitute status. |
Name | Type | Description |
Success | String | Returns true if procedure succeeded. |
Updates pull request comment information.Authenticated user can update his own comments.
Name | Type | Required | Description |
ProjectId | String | True | Id of the project. |
RepositoryId | String | True | Id of the repository. |
Number | String | True | Number of the pull request. |
CommentId | String | True | Id of the comment. |
Content | String | True | Content of the comment. |
Name | Type | Description |
Success | String | Returns True if procedure succeeded. |
Updates space notification.
Name | Type | Required | Description |
Content | String | True | Content of the update. |
Name | Type | Description |
Success | String | Returns True if the update succeeded. |
You can query the system tables described in this section to access schema information, information on data source functionality, and batch operation statistics.
The following tables return database metadata for Backlog:
The following tables return information about how to connect to and query the data source:
The following table returns query statistics for data modification queries:
Lists the available databases.
The following query retrieves all databases determined by the connection string:
SELECT * FROM sys_catalogs
Name | Type | Description |
CatalogName | String | The database name. |
Lists the available schemas.
The following query retrieves all available schemas:
SELECT * FROM sys_schemas
Name | Type | Description |
CatalogName | String | The database name. |
SchemaName | String | The schema name. |
Lists the available tables.
The following query retrieves the available tables and views:
SELECT * FROM sys_tables
Name | Type | Description |
CatalogName | String | The database containing the table or view. |
SchemaName | String | The schema containing the table or view. |
TableName | String | The name of the table or view. |
TableType | String | The table type (table or view). |
Description | String | A description of the table or view. |
IsUpdateable | Boolean | Whether the table can be updated. |
Describes the columns of the available tables and views.
The following query returns the columns and data types for the Issues table:
SELECT ColumnName, DataTypeName FROM sys_tablecolumns WHERE TableName='Issues'
Name | Type | Description |
CatalogName | String | The name of the database containing the table or view. |
SchemaName | String | The schema containing the table or view. |
TableName | String | The name of the table or view containing the column. |
ColumnName | String | The column name. |
DataTypeName | String | The data type name. |
DataType | Int32 | An integer indicating the data type. This value is determined at run time based on the environment. |
Length | Int32 | The storage size of the column. |
DisplaySize | Int32 | The designated column's normal maximum width in characters. |
NumericPrecision | Int32 | The maximum number of digits in numeric data. The column length in characters for character and date-time data. |
NumericScale | Int32 | The column scale or number of digits to the right of the decimal point. |
IsNullable | Boolean | Whether the column can contain null. |
Description | String | A brief description of the column. |
Ordinal | Int32 | The sequence number of the column. |
IsAutoIncrement | String | Whether the column value is assigned in fixed increments. |
IsGeneratedColumn | String | Whether the column is generated. |
IsHidden | Boolean | Whether the column is hidden. |
IsArray | Boolean | Whether the column is an array. |
IsReadOnly | Boolean | Whether the column is read-only. |
IsKey | Boolean | Indicates whether a field returned from sys_tablecolumns is the primary key of the table. |
Lists the available stored procedures.
The following query retrieves the available stored procedures:
SELECT * FROM sys_procedures
Name | Type | Description |
CatalogName | String | The database containing the stored procedure. |
SchemaName | String | The schema containing the stored procedure. |
ProcedureName | String | The name of the stored procedure. |
Description | String | A description of the stored procedure. |
ProcedureType | String | The type of the procedure, such as PROCEDURE or FUNCTION. |
Describes stored procedure parameters.
The following query returns information about all of the input parameters for the AddStar stored procedure:
SELECT * FROM sys_procedureparameters WHERE ProcedureName='AddStar' AND Direction=1 OR Direction=2
Name | Type | Description |
CatalogName | String | The name of the database containing the stored procedure. |
SchemaName | String | The name of the schema containing the stored procedure. |
ProcedureName | String | The name of the stored procedure containing the parameter. |
ColumnName | String | The name of the stored procedure parameter. |
Direction | Int32 | An integer corresponding to the type of the parameter: input (1), input/output (2), or output(4). input/output type parameters can be both input and output parameters. |
DataTypeName | String | The name of the data type. |
DataType | Int32 | An integer indicating the data type. This value is determined at run time based on the environment. |
Length | Int32 | The number of characters allowed for character data. The number of digits allowed for numeric data. |
NumericPrecision | Int32 | The maximum precision for numeric data. The column length in characters for character and date-time data. |
NumericScale | Int32 | The number of digits to the right of the decimal point in numeric data. |
IsNullable | Boolean | Whether the parameter can contain null. |
IsRequired | Boolean | Whether the parameter is required for execution of the procedure. |
IsArray | Boolean | Whether the parameter is an array. |
Description | String | The description of the parameter. |
Ordinal | Int32 | The index of the parameter. |
Describes the primary and foreign keys.
The following query retrieves the primary key for the Issues table:
SELECT * FROM sys_keycolumns WHERE IsKey='True' AND TableName='Issues'
Name | Type | Description |
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
IsKey | Boolean | Whether the column is a primary key in the table referenced in the TableName field. |
IsForeignKey | Boolean | Whether the column is a foreign key referenced in the TableName field. |
PrimaryKeyName | String | The name of the primary key. |
ForeignKeyName | String | The name of the foreign key. |
ReferencedCatalogName | String | The database containing the primary key. |
ReferencedSchemaName | String | The schema containing the primary key. |
ReferencedTableName | String | The table containing the primary key. |
ReferencedColumnName | String | The column name of the primary key. |
Describes the foreign keys.
The following query retrieves all foreign keys which refer to other tables:
SELECT * FROM sys_foreignkeys WHERE ForeignKeyType = 'FOREIGNKEY_TYPE_IMPORT'
Name | Type | Description |
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
PrimaryKeyName | String | The name of the primary key. |
ForeignKeyName | String | The name of the foreign key. |
ReferencedCatalogName | String | The database containing the primary key. |
ReferencedSchemaName | String | The schema containing the primary key. |
ReferencedTableName | String | The table containing the primary key. |
ReferencedColumnName | String | The column name of the primary key. |
ForeignKeyType | String | Designates whether the foreign key is an import (points to other tables) or export (referenced from other tables) key. |
Describes the primary keys.
The following query retrieves the primary keys from all tables and views:
SELECT * FROM sys_primarykeys
Name | Type | Description |
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
KeySeq | String | The sequence number of the primary key. |
KeyName | String | The name of the primary key. |
Describes the available indexes. By filtering on indexes, you can write more selective queries with faster query response times.
The following query retrieves all indexes that are not primary keys:
SELECT * FROM sys_indexes WHERE IsPrimary='false'
Name | Type | Description |
CatalogName | String | The name of the database containing the index. |
SchemaName | String | The name of the schema containing the index. |
TableName | String | The name of the table containing the index. |
IndexName | String | The index name. |
ColumnName | String | The name of the column associated with the index. |
IsUnique | Boolean | True if the index is unique. False otherwise. |
IsPrimary | Boolean | True if the index is a primary key. False otherwise. |
Type | Int16 | An integer value corresponding to the index type: statistic (0), clustered (1), hashed (2), or other (3). |
SortOrder | String | The sort order: A for ascending or D for descending. |
OrdinalPosition | Int16 | The sequence number of the column in the index. |
Returns information on the available connection properties and those set in the connection string.
When querying this table, the config connection string should be used:
jdbc:cdata:backlog:config:
This connection string enables you to query this table without a valid connection.
The following query retrieves all connection properties that have been set in the connection string or set through a default value:
SELECT * FROM sys_connection_props WHERE Value <> ''
Name | Type | Description |
Name | String | The name of the connection property. |
ShortDescription | String | A brief description. |
Type | String | The data type of the connection property. |
Default | String | The default value if one is not explicitly set. |
Values | String | A comma-separated list of possible values. A validation error is thrown if another value is specified. |
Value | String | The value you set or a preconfigured default. |
Required | Boolean | Whether the property is required to connect. |
Category | String | The category of the connection property. |
IsSessionProperty | String | Whether the property is a session property, used to save information about the current connection. |
Sensitivity | String | The sensitivity level of the property. This informs whether the property is obfuscated in logging and authentication forms. |
PropertyName | String | A camel-cased truncated form of the connection property name. |
Ordinal | Int32 | The index of the parameter. |
CatOrdinal | Int32 | The index of the parameter category. |
Hierarchy | String | Shows dependent properties associated that need to be set alongside this one. |
Visible | Boolean | Informs whether the property is visible in the connection UI. |
ETC | String | Various miscellaneous information about the property. |
Describes the SELECT query processing that the Cloud can offload to the data source.
See SQL Compliance for SQL syntax details.
Below is an example data set of SQL capabilities. Some aspects of SELECT functionality are returned in a comma-separated list if supported; otherwise, the column contains NO.
Name | Description | Possible Values |
AGGREGATE_FUNCTIONS | Supported aggregation functions. | AVG, COUNT, MAX, MIN, SUM, DISTINCT |
COUNT | Whether COUNT function is supported. | YES, NO |
IDENTIFIER_QUOTE_OPEN_CHAR | The opening character used to escape an identifier. | [ |
IDENTIFIER_QUOTE_CLOSE_CHAR | The closing character used to escape an identifier. | ] |
SUPPORTED_OPERATORS | A list of supported SQL operators. | =, >, <, >=, <=, <>, !=, LIKE, NOT LIKE, IN, NOT IN, IS NULL, IS NOT NULL, AND, OR |
GROUP_BY | Whether GROUP BY is supported, and, if so, the degree of support. | NO, NO_RELATION, EQUALS_SELECT, SQL_GB_COLLATE |
OJ_CAPABILITIES | The supported varieties of outer joins supported. | NO, LEFT, RIGHT, FULL, INNER, NOT_ORDERED, ALL_COMPARISON_OPS |
OUTER_JOINS | Whether outer joins are supported. | YES, NO |
SUBQUERIES | Whether subqueries are supported, and, if so, the degree of support. | NO, COMPARISON, EXISTS, IN, CORRELATED_SUBQUERIES, QUANTIFIED |
STRING_FUNCTIONS | Supported string functions. | LENGTH, CHAR, LOCATE, REPLACE, SUBSTRING, RTRIM, LTRIM, RIGHT, LEFT, UCASE, SPACE, SOUNDEX, LCASE, CONCAT, ASCII, REPEAT, OCTET, BIT, POSITION, INSERT, TRIM, UPPER, REGEXP, LOWER, DIFFERENCE, CHARACTER, SUBSTR, STR, REVERSE, PLAN, UUIDTOSTR, TRANSLATE, TRAILING, TO, STUFF, STRTOUUID, STRING, SPLIT, SORTKEY, SIMILAR, REPLICATE, PATINDEX, LPAD, LEN, LEADING, KEY, INSTR, INSERTSTR, HTML, GRAPHICAL, CONVERT, COLLATION, CHARINDEX, BYTE |
NUMERIC_FUNCTIONS | Supported numeric functions. | ABS, ACOS, ASIN, ATAN, ATAN2, CEILING, COS, COT, EXP, FLOOR, LOG, MOD, SIGN, SIN, SQRT, TAN, PI, RAND, DEGREES, LOG10, POWER, RADIANS, ROUND, TRUNCATE |
TIMEDATE_FUNCTIONS | Supported date/time functions. | NOW, CURDATE, DAYOFMONTH, DAYOFWEEK, DAYOFYEAR, MONTH, QUARTER, WEEK, YEAR, CURTIME, HOUR, MINUTE, SECOND, TIMESTAMPADD, TIMESTAMPDIFF, DAYNAME, MONTHNAME, CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, EXTRACT |
REPLICATION_SKIP_TABLES | Indicates tables skipped during replication. | |
REPLICATION_TIMECHECK_COLUMNS | A string array containing a list of columns which will be used to check for (in the given order) to use as a modified column during replication. | |
IDENTIFIER_PATTERN | String value indicating what string is valid for an identifier. | |
SUPPORT_TRANSACTION | Indicates if the provider supports transactions such as commit and rollback. | YES, NO |
DIALECT | Indicates the SQL dialect to use. | |
KEY_PROPERTIES | Indicates the properties which identify the uniform database. | |
SUPPORTS_MULTIPLE_SCHEMAS | Indicates if multiple schemas may exist for the provider. | YES, NO |
SUPPORTS_MULTIPLE_CATALOGS | Indicates if multiple catalogs may exist for the provider. | YES, NO |
DATASYNCVERSION | The CData Data Sync version needed to access this driver. | Standard, Starter, Professional, Enterprise |
DATASYNCCATEGORY | The CData Data Sync category of this driver. | Source, Destination, Cloud Destination |
SUPPORTSENHANCEDSQL | Whether enhanced SQL functionality beyond what is offered by the API is supported. | TRUE, FALSE |
SUPPORTS_BATCH_OPERATIONS | Whether batch operations are supported. | YES, NO |
SQL_CAP | All supported SQL capabilities for this driver. | SELECT, INSERT, DELETE, UPDATE, TRANSACTIONS, ORDERBY, OAUTH, ASSIGNEDID, LIMIT, LIKE, BULKINSERT, COUNT, BULKDELETE, BULKUPDATE, GROUPBY, HAVING, AGGS, OFFSET, REPLICATE, COUNTDISTINCT, JOINS, DROP, CREATE, DISTINCT, INNERJOINS, SUBQUERIES, ALTER, MULTIPLESCHEMAS, GROUPBYNORELATION, OUTERJOINS, UNIONALL, UNION, UPSERT, GETDELETED, CROSSJOINS, GROUPBYCOLLATE, MULTIPLECATS, FULLOUTERJOIN, MERGE, JSONEXTRACT, BULKUPSERT, SUM, SUBQUERIESFULL, MIN, MAX, JOINSFULL, XMLEXTRACT, AVG, MULTISTATEMENTS, FOREIGNKEYS, CASE, LEFTJOINS, COMMAJOINS, WITH, LITERALS, RENAME, NESTEDTABLES, EXECUTE, BATCH, BASIC, INDEX |
PREFERRED_CACHE_OPTIONS | A string value specifies the preferred cacheOptions. | |
ENABLE_EF_ADVANCED_QUERY | Indicates if the driver directly supports advanced queries coming from Entity Framework. If not, queries will be handled client side. | YES, NO |
PSEUDO_COLUMNS | A string array indicating the available pseudo columns. | |
MERGE_ALWAYS | If the value is true, The Merge Mode is forcibly executed in Data Sync. | TRUE, FALSE |
REPLICATION_MIN_DATE_QUERY | A select query to return the replicate start datetime. | |
REPLICATION_MIN_FUNCTION | Allows a provider to specify the formula name to use for executing a server side min. | |
REPLICATION_START_DATE | Allows a provider to specify a replicate startdate. | |
REPLICATION_MAX_DATE_QUERY | A select query to return the replicate end datetime. | |
REPLICATION_MAX_FUNCTION | Allows a provider to specify the formula name to use for executing a server side max. | |
IGNORE_INTERVALS_ON_INITIAL_REPLICATE | A list of tables which will skip dividing the replicate into chunks on the initial replicate. | |
CHECKCACHE_USE_PARENTID | Indicates whether the CheckCache statement should be done against the parent key column. | TRUE, FALSE |
CREATE_SCHEMA_PROCEDURES | Indicates stored procedures that can be used for generating schema files. |
The following query retrieves the operators that can be used in the WHERE clause:
SELECT * FROM sys_sqlinfo WHERE Name = 'SUPPORTED_OPERATORS'
Note that individual tables may have different limitations or requirements on the WHERE clause; refer to the Data Model section for more information.
Name | Type | Description |
NAME | String | A component of SQL syntax, or a capability that can be processed on the server. |
VALUE | String | Detail on the supported SQL or SQL syntax. |
Returns information about attempted modifications.
The following query retrieves the Ids of the modified rows in a batch operation:
SELECT * FROM sys_identity
Name | Type | Description |
Id | String | The database-generated Id returned from a data modification operation. |
Batch | String | An identifier for the batch. 1 for a single operation. |
Operation | String | The result of the operation in the batch: INSERTED, UPDATED, or DELETED. |
Message | String | SUCCESS or an error message if the update in the batch failed. |
The connection string properties are the various options that can be used to establish a connection. This section provides a complete list of the options you can configure in the connection string for this provider. Click the links for further details.
For more information on establishing a connection, see Establishing a Connection.
Property | Description |
URL | The URL of the Backlog account. |
AuthScheme | The type of authentication to use when connecting to Backlog. |
ApiKey | The API key allows you make requests to the Backlog API. |
Property | Description |
OAuthClientId | The client Id assigned when you register your application with an OAuth authorization server. |
OAuthClientSecret | The client secret assigned when you register your application with an OAuth authorization server. |
Property | Description |
SSLServerCert | The certificate to be accepted from the server when connecting using TLS/SSL. |
Property | Description |
Verbosity | The verbosity level that determines the amount of detail included in the log file. |
Property | Description |
BrowsableSchemas | This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC. |
Property | Description |
IncludeCustomFields | Set this to true if you want to retrieve custom fields from the Issues table. |
MaxRows | Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses. |
MaxThreads | The Max Thread. |
Pagesize | The maximum number of results to return per page from Backlog. |
ProjectId | Id of the specific project. |
PseudoColumns | This property indicates whether or not to include pseudo columns as columns to the table. |
Timeout | The value in seconds until the timeout error is thrown, canceling the operation. |
This section provides a complete list of the Authentication properties you can configure in the connection string for this provider.
Property | Description |
URL | The URL of the Backlog account. |
AuthScheme | The type of authentication to use when connecting to Backlog. |
ApiKey | The API key allows you make requests to the Backlog API. |
The URL of the Backlog account.
string
""
The URL of the Backlog account in the form "https://{sample}.backlog.com".
The type of authentication to use when connecting to Backlog.
string
"APIToken"
The API key allows you make requests to the Backlog API.
string
""
Append your API key to the API requests to return data from your account.
This section provides a complete list of the OAuth properties you can configure in the connection string for this provider.
Property | Description |
OAuthClientId | The client Id assigned when you register your application with an OAuth authorization server. |
OAuthClientSecret | The client secret assigned when you register your application with an OAuth authorization server. |
The client Id assigned when you register your application with an OAuth authorization server.
string
""
As part of registering an OAuth application, you will receive the OAuthClientId value, sometimes also called a consumer key, and a client secret, the OAuthClientSecret.
The client secret assigned when you register your application with an OAuth authorization server.
string
""
As part of registering an OAuth application, you will receive the OAuthClientId, also called a consumer key. You will also receive a client secret, also called a consumer secret. Set the client secret in the OAuthClientSecret property.
This section provides a complete list of the SSL properties you can configure in the connection string for this provider.
Property | Description |
SSLServerCert | The certificate to be accepted from the server when connecting using TLS/SSL. |
The certificate to be accepted from the server when connecting using TLS/SSL.
string
""
If using a TLS/SSL connection, this property can be used to specify the TLS/SSL certificate to be accepted from the server. Any other certificate that is not trusted by the machine is rejected.
This property can take the following forms:
Description | Example |
A full PEM Certificate (example shortened for brevity) | -----BEGIN CERTIFICATE----- MIIChTCCAe4CAQAwDQYJKoZIhv......Qw== -----END CERTIFICATE----- |
A path to a local file containing the certificate | C:\cert.cer |
The public key (example shortened for brevity) | -----BEGIN RSA PUBLIC KEY----- MIGfMA0GCSq......AQAB -----END RSA PUBLIC KEY----- |
The MD5 Thumbprint (hex values can also be either space or colon separated) | ecadbdda5a1529c58a1e9e09828d70e4 |
The SHA1 Thumbprint (hex values can also be either space or colon separated) | 34a929226ae0819f2ec14b4a3d904f801cbb150d |
If not specified, any certificate trusted by the machine is accepted.
Use '*' to signify to accept all certificates. Note that this is not recommended due to security concerns.
This section provides a complete list of the Logging properties you can configure in the connection string for this provider.
Property | Description |
Verbosity | The verbosity level that determines the amount of detail included in the log file. |
The verbosity level that determines the amount of detail included in the log file.
string
"1"
The verbosity level determines the amount of detail that the Cloud reports to the Logfile. Verbosity levels from 1 to 5 are supported. These are detailed in the Logging page.
This section provides a complete list of the Schema properties you can configure in the connection string for this provider.
Property | Description |
BrowsableSchemas | This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC. |
This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC.
string
""
Listing the schemas from databases can be expensive. Providing a list of schemas in the connection string improves the performance.
This section provides a complete list of the Miscellaneous properties you can configure in the connection string for this provider.
Property | Description |
IncludeCustomFields | Set this to true if you want to retrieve custom fields from the Issues table. |
MaxRows | Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses. |
MaxThreads | The Max Thread. |
Pagesize | The maximum number of results to return per page from Backlog. |
ProjectId | Id of the specific project. |
PseudoColumns | This property indicates whether or not to include pseudo columns as columns to the table. |
Timeout | The value in seconds until the timeout error is thrown, canceling the operation. |
Set this to true if you want to retrieve custom fields from the Issues table.
bool
false
If set to true, the ProjectId connection property is also required.
Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses.
int
-1
Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses.
The Max Thread.
string
"1"
The maximum number of results to return per page from Backlog.
int
100
The Pagesize property affects the maximum number of results to return per page from Backlog. Setting a higher value may result in better performance at the cost of additional memory allocated per page consumed.
Id of the specific project.
string
""
Id of the specific project.
This property indicates whether or not to include pseudo columns as columns to the table.
string
""
This setting is particularly helpful in Entity Framework, which does not allow you to set a value for a pseudo column unless it is a table column. The value of this connection setting is of the format "Table1=Column1, Table1=Column2, Table2=Column3". You can use the "*" character to include all tables and all columns; for example, "*=*".
The value in seconds until the timeout error is thrown, canceling the operation.
int
60
If Timeout = 0, operations do not time out. The operations run until they complete successfully or until they encounter an error condition.
If Timeout expires and the operation is not yet complete, the Cloud throws an exception.