type Statement (v202411)

  • The Statement object defines the WHERE, ORDER BY, and LIMIT clauses for PQL queries used to retrieve specific objects.

  • It utilizes bind variables as placeholders for literal values, enabling dynamic query construction.

  • The query field holds the PQL syntax, while the values field stores the corresponding values for bind variables.

  • Statements allow wildcard string matching through the LIKE keyword for flexible filtering.

  • Bind variable values are set using specific Value objects like TextValue, NumberValue, and BooleanValue, depending on the variable type.
Service
AdRuleService AdjustmentService AudienceSegmentService CdnConfigurationService CmsMetadataService CompanyService ContactService ContentBundleService ContentService CreativeService CreativeSetService CreativeTemplateService CreativeWrapperService CustomFieldService CustomTargetingService DaiAuthenticationKeyService DaiEncodingProfileService InventoryService LabelService LineItemCreativeAssociationService LineItemService LineItemTemplateService LiveStreamEventService MobileApplicationService NativeStyleService OrderService PlacementService ProposalLineItemService ProposalService PublisherQueryLanguageService ReportService SiteService StreamActivityMonitorService SuggestedAdUnitService TargetingPresetService TeamService UserService UserTeamAssociationService YieldGroupService
Dependencies
getMarketplaceCommentsBySta... getProposalsByStatement() performProposalAction()
▼
Statement

Captures the WHERE, ORDER BY and LIMIT clauses of a PQL query. Statements are typically used to retrieve objects of a predefined domain type, which makes SELECT clause unnecessary.

An example query text might be "WHERE status = 'ACTIVE' ORDER BY id LIMIT 30".

Statements support bind variables. These are substitutes for literals and can be thought of as input parameters to a PQL query.

An example of such a query might be "WHERE id = :idValue".

Statements also support use of the LIKE keyword. This provides wildcard string matching.

An example of such a query might be "WHERE name LIKE '%searchString%'".

The value for the variable idValue must then be set with an object of type Value, e.g., NumberValue, TextValue or BooleanValue.
Namespace
https://www.google.com/apis/ads/publisher/v202411

Field

query

xsd:string

Holds the query in PQL syntax. The syntax is:
[WHERE <condition> {[AND | OR] <condition> ...}]
[ORDER BY <property> [ASC | DESC]]
[LIMIT {[<offset>,] <count>} | {<count> OFFSET <offset>}]

<condition>
     := <property> {< | <= | > | >= | = | != } <value>
<condition>
     := <property> {< | <= | > | >= | = | != } <bind variable>
<condition> := <property> IN <list>
<condition> := <property> IS NULL
<condition> := <property> LIKE <wildcard%match>
<bind variable> := :<name>

values

String_ValueMapEntry[]

Holds keys and values for bind variables and their values. The key is the name of the bind variable. The value is the literal value of the variable.

In the example "WHERE status = :bindStatus ORDER BY id LIMIT 30", the bind variable, represented by :bindStatus is named bindStatus, which would also be the parameter map key. The bind variable's value would be represented by a parameter map value of type TextValue. The final result, for example, would be an entry of "bindStatus" => StringParam("ACTIVE").