Marek Madejski

Results 32 issues of Marek Madejski

The following query works as expected: ```apex new QueryBuilder(Account.class) .addField(Account.Name) .addConditions() .add(new QueryBuilder.SimpleCondition('Name = \'acc1\'')) .add(new QueryBuilder.SimpleCondition('Name = \'acc2\'')) .add(new QueryBuilder.SimpleCondition('Name = \'acc3\'')) .add(new QueryBuilder.SimpleCondition('Name = \'acc4\'')) (...) .add(new QueryBuilder.SimpleCondition('Name...

The operators [INCLUDES and EXCLUDES](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_select_comparisonoperators.htm), essential for the mutipicklists, are not currently supported by this framework. Please add them, preferably as `extends FieldCondition`.

### Summary There is a new type of token ("fine-grained"), and the older ones are called "classic", which this tutorial is not aware of. ### How to reproduce 1. Complete...

bug

I see not way to introduce `NOT` operator (not to be confused with `NOT IN`) in the `WHERE` part, otherwise than rewriting the query. Example: ```sql WHERE NOT (Industry =...

There is no `NOT LIKE` operator in SOQL. The following fails on the query: ```apex new Query(Account.SObjectType) .filterWhere(new SOQL.QueryFilter(Account.Name, SOQL.Operator.IS_NOT_LIKE, 'xyz')) .getResults() ``` The correct syntax is `NOT Field__c LIKE...

I see not way to introduce `NOT` operator (not to be confused with `NOT IN`) in the `WHERE` part, otherwise than rewriting the query. Example: ```sql WHERE NOT (Industry =...

```apex System.debug( new Query(Task.SObjectType) .addPolymorphicFields( Task.WhoId, new Map{ Contact.SObjectType => new List{} } ) .getQuery() ); ``` When `addPolymorphicFields(SObjectField, Map)` or `addPolymorphicFields(SObjectField, Map)` is used with a non-empty map, but...

```apex System.debug( new Query(Case.SObjectType) .addPolymorphicFields(Case.OwnerId) .getQuery() ); ``` result: ```sql SELECT CaseNumber, Id, Who.Alias, Who.Email, Who.FirstName, (a lot of Who.X fields) FROM Case ``` Obviously, such a query will fail....