dotConnect for BigCommerce can translate a subset of SQL-92 SELECT statements to the corresponding BigCommerce API calls for remote execution. As remote execution provides much higher performance than local one, it makes sense to use SELECT statements that are translatable to API Calls.

SELECT statements that correspond to the following pattern and conditions can be converted to API calls and executed remotely:

SELECT result_columns FROM table [WHERE where_condition]  [LIMIT count OFFSET offset]

• result_columns can be a list of the columns, separated with commas, or "*", which means all the result columns or the count(*) aggregation functions (it must be the only column requested).
• table - the name of the BigCommerce object.
• where_condition - one or more conditions, united with 'AND'. Condition must be a comparison of a column of the selected object and a constant or a parameter. No arithmetic or other functions are allowed. The following comparison operators are supported: =, <=, >=, . Only the columns that allows filtering can be included in where_condition

If a SELECT statement contains any of the features, not explicitly mentioned above, it cannot be translated to BigCommerce API calls and by default, it is executed locally, which usually takes more time and resources than remote execution. (Local execution can be disabled completely if necessary - see Select Statement Execution).

Exceptions

If a statement contains any of the exceptions, listed below, it also cannot be translated to the BigCommerce API calls and is executed locally.

• Querying the number of records ("COUNT(*)") cannot be converted to API calls for the following objects: BlogTags, OrderCoupons, OrderMessages, OrderStatuses, OrderTaxes, PaymentMethods, ProductGoogleProductSearch, OptionSetsOptions, OptionValues, ProductOptions, ProductReviews, ShippingMethods, Store, TaxClasses.

Filterable Columns and Allowed Comparison Operators