Generated schema file..

Table Specific Information

Select

The cmdlet uses the Azure DevOps API to process WHERE clause conditions built with the following columns and operators:

• Id supports the '=' operator.
• ProjectId supports the '=' operator.
• IncludeAllUrls supports the '=' operator.
• IncludeHidden supports the '=' operator.
• IncludeLinks supports the '=' operator.
• IncludeParent supports the '=' operator.

The rest of the filter is executed client-side in the cmdlet.

For example:

	SELECT * FROM Repositories WHERE Id = '02b4a62d-2f5f-4d69-8420-29257dcc8051'
	SELECT * FROM Repositories WHERE ProjectId = '837ccd31-8159-4db3-b8ce-de0c36d2a0bf'
	SELECT * FROM Repositories WHERE IncludeAllUrls = true
	SELECT * FROM Repositories WHERE IncludeLinks = true

Insert

The following is an example of inserting into a Repositories table:

INSERT INTO Repositories (ProjectId, Name) VALUES ('c831d3b4-a289-462f', 'TestRepository')

Update

The following is an example of updating a Repositories table:

UPDATE Repositories SET Name = 'cdata2' WHERE Id = 'dbf5e1ff-9192-4f94-ba21-735a4c289c72' AND ProjectId = 'b154d8f3-bfd9-4bfb-90ae-2e6c8cda8937'

Delete

The following is an example of deleting data in a Repositories table:

DELETE FROM Repositories WHERE Id = 'dbf5e1ff-9192-4f94-ba21-735a4c289c72' AND ProjectId = 'b154d8f3-bfd9-4bfb-90ae-2e6c8cda8937'

Columns

Pseudo-Columns

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. Unless otherwise specified, only the = operator is permitted when filtering on pseudocolumns.