You can increase the timeout value. One of the properties of any query is CommandTimeout, See Reference Help regarding the IEntityQuery interface.. Public Properties
|
Name |
Description |
|
about:blankIdeaBlade.Persistence~IdeaBlade.Persistence.IEntityQuery~CommandTimeout.html - CommandTimeout |
Gets or sets the timeout value for the command. |
|
about:blankIdeaBlade.Persistence~IdeaBlade.Persistence.IEntityQuery~EntityType.html - EntityType |
The entity type that this query returns. |
|
about:blankIdeaBlade.Persistence~IdeaBlade.Persistence.IEntityQuery~FindRowsResultMode.html - FindRowsResultMode |
Returns information regarding the behaviour of the about:blankIdeaBlade.Persistence~IdeaBlade.Persistence.IEntityQuery~FindRows.html - FindRows method call. |
|
about:blankIdeaBlade.Persistence~IdeaBlade.Persistence.IEntityQuery~QueryStrategy.html - QueryStrategy |
Determines whether this query will operate against the data source, the in-memory cache, or a combination of the two. |
If you want to avoid such timeout, you should try to break down some of the more complicated span queries into several smaller separate span queries.
Assuming you have 3 different relationships to the current entity table, you would normally create a span query with 3 separate AddSpan clauses to retrieve data from all 4 tables. You could try to break them up into 3 separate span queries instead.
|