Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Since your predicate or filter object is an array just test the length. If it is zero then don't apply the where clause. You have already defined query so there is no need to do anything else.</p> <pre><code>function getAll(predicate, dataObservable) { var query = breeze.EntityQuery.from('Data'); if (breeze.Predicate.isPredicate(predicate) &amp;&amp; predicate.length !==0) { query = query.where(predicate); } return manager.executeQuery(query).then(success).fail(failure); } </code></pre> <p><strong>EDIT</strong></p> <p>In your question I realize you stated you can refactor your code after I provided this answer. Without going into too much detail, I choose to create re-usable queries that can be dynamically created to reduce how much code must be changed if I change my model. It seems that is what you are trying to do as well. I would recommend building a query that is robust enough to take in predicates, an orderBy, a take, and anything else you <em>may</em> use later, and then handle if the passed in objects or variables are null. I feel this is the best approach for writing reusable code. Example - </p> <pre><code>function getEntities(dataObservable, predicates, orderby, take, local) { var query = breeze.EntityQuery.from('Data'); if (local) { query = query.executeQueryLocally(); } if (orderBy) { query = query.orderBy(orderby); } if (take) { query = query.take(take); } if (breeze.Predicate.isPredicate(predicate) &amp;&amp; predicate.length !==0) { query = query.where(predicate); } return manager.executeQuery(query).then(success).fail(failure); } </code></pre> <p>By doing this each subsequent time you need to filter data you can define methods in your data service or directly from your view model to follow the fetch pattern. Now when you go back and change your model or something you have one query to adjust instead of 20.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow can I test for an empty Breeze predicate?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPW Kad
    1. USPW Kad
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow can I test for an empty Breeze predicate?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload