CustomRepository

Enumeration of all condition types. This enumeration defines a set of String values. It exists primarily for documentation purposes - in code use the actual string values like '>', don't reference them through this class like WhereCondition.more.

We define several aliases for the same condition. In case of direct HTTP request (without Repository) use only non-aliased values (i.e. more instead of '>' or 'gt')

Retrieve a data from server using methodName entity method. By default select method will be used.

Add fields to collection. Can take one attribute name as string or array of attributes. Duplicate is not checked and in case of duplicate attribute caller got server error.

 UB.Repository('tri_srf_reg').attrs('ID').attrs(['code', 'name']).attrs('fullName', 'newCode');

Can take expression as a field. In this case entity attribute name must be wrapped into [] brackets. In case of client-side execution the only valid expression is one of:

• 'SUM', 'COUNT', 'AVG', 'MAX', 'MIN', 'CAST', 'COALESCE'

Example:

 UB.Repository('tri_srf_reg').attrs('SUM([payment])').where('documentID', '=', value); //will calculate sum of document payments

If case of server-side execution any valid SQL expression is accepted:

 UB.Repository('uba_user').attrs('[ID] / 100 + 1').selectAsArray()

Add where expression. Fix some known issues:

• if attribute name without brackets is passed to expression parameter then wrap attribute to brackets "ID" -> "[ID]"

• transform some dummy expressions to more simple form: in ['one'] -> equal 'one',in []->0=1,? null->isNull` e.t.c.

• expression may contains this functions: 'SUM', 'COUNT', 'AVG', 'MAX', 'MIN', 'CAST', 'COALESCE', 'LENGTH', 'LOWER', 'UPPER', 'DAY', 'MONTH', 'YEAR', 'ROUND', 'FLOOR', 'CEILING'

In and 'notIn` conditions can take a sub-repository as a values parameter value. See CustomRepository.exists for a conplex example

UB.Repository('my_entity').attrs('id')
          .where('code', 'in', ['1', '2', '3'])  // code in ('1', '2', '3')
          .where('code', 'in', UB.Repository('my_codes').attr('code').where('ID', '<', 10)  // code in (select code from my_codes where id = 10)
          .where('[name]', 'contains', 'Homer'). // name like '%homer%'
          .where('[birtday]', 'geq', new Date()).where('birtday', 'leq', new Date() + 10) //(birtday >= '2012-01-01') AND (birtday <= '2012-01-02')
          .where('[age] -10', '>=', {age: 15}, 'byAge') // (age + 10 >= 15)
          .where('LENGTH([code]), '<', 5)
          .where('', 'match', 'myvalue') // for condition match expression not need

Add an expression with EXISTS sub-query. Inside a sub-query there is two macro:

• {master} will be replaced by master entity alias

• {self} will be replaced by sub-query entity alias

  //select users UB.Repository('uba_user').attrs(['ID', 'name'])

  // who are not disabled
  .where('disabled', '=', 0)
  // which allowed access from Kiev
  .where('trustedIP', 'in',
    UB.Repository('geo_ip').attrs('IPAddr')
      .where('city', '=', 'Kiev')
  )
  // who do not login during this year
  .notExists(
    UB.Repository('uba_audit')
      .correlation('actionUser', 'name')  // here we link to uba_user.name
      .where('actionTime', '>', new Date(2016, 1, 1))
      .where('actionType', '=', 'LOGIN')
  )
  // but modify some data
  .exists(
    UB.Repository('ubs_audit')
      .correlation('actionUser', 'ID') // here we link to uba_user.ID
      .where('actionTime', '>', new Date(2016, 1, 1))
  )
  .select()

Add an expression with NOT EXISTS sub-query. See CustomRepository.exists for sample

If current repository are used as a sub-query for exists, notExists, in or notIn conditions will add a correlation with a master repository

Arrange where expressions in logical order. By default where expressions is joined by AND logical predicate. Here is possible to join it in custom order.

 UB.Repository('my_entity').attrs('id')
     .where('code', 'in', ['1', '2', '3'], 'byCode')  // code in ('1', '2', '3')
     .where('name', 'contains', 'Homer', 'byName') // name like '%homer%'
     .where('birtday', 'geq', new Date()).where('birtday', 'leq', new Date() + 10) //(birtday >= '2012-01-01') AND (birtday <= '2012-01-02')
     .where('[age] -10', '>=', {age: 15}, 'byAge') // (age + 10 >= 15)
     .logic('(([byCode]) OR ([byName]))') // (byCode OR byName) AND (all where items, not included in logic)

Force where expressions to be used in join SQL statement instead of where. Applicable only for not cached entities.

 // will generate
 // SELECT A.ID, B.code FROM tst_document A LEFT JOIN tst_category B ON (B.instanceID = A.ID and B.ubUser = 10)
 // instead of
 // SELECT A.ID, B.code FROM tst_document A LEFT JOIN tst_category B ON B.instanceID = A.ID WHERE B.ubUser = 10
 UB.Repository('tst_document').attrs(['ID', '[caregory.code]'])
     .where('[caregory.ubUser]', '=', 10, 'wantInJoin')
     .join('wantInJoin')
     .selectAsObject().done(UB.logDebug);

Add join condition. Fix some known issues

Add sorting

 UB.CustomRepository('my_entity').attrs('ID').orderBy('code')

Add desc sorting. The same as orderBy(attr, 'desc')

 UB.Repository('my_entity').attrs('ID').orderBy('code').orderByDesc('date_create') // ORDER BY code, date_create DESC

Add grouping Can take one attribute name as string or array of attributes name

 UB.Repository('my_entity').attrs('ID').groupBy('code')
 UB.Repository('uba_user').attrs('disabled').groupBy('disabled').select()
 UB.Repository('uba_user').attrs(['disabled','uPassword','COUNT([ID])']).groupBy(['disabled','uPassword']).select()

Add options.start value to retrieve first start rows

 var store = UB.Repository('my_entity').attrs('id').start(15).limit(10).select() //will return ID's from 15 to 25

Add options.limit value. Can be combined with {@link CustomRepository#start).

 var store = UB.CRepository('my_entity').attrs('id').limit(2).select() ; //will return first two ID's from my_entity

For debug purpose only.

If set, in GUI mode will put this description into log before query execution

 var store = UB.Repository('my_entity').attrs('ID').describe('Select all record for "my_entity"').select()

Construct a UBQL JSON request. Used in CustomRepository#select

  var repo = UB.Repository('my_entity').attrs('ID').where('code', '=', 'a')
  var inst = new TubDataStore(my_entity);
  inst.run('select', repo.ubql());

Must be implemented in descendants and return (or resolved for async clients) to array of object representation of result, like this

 [{"ID":3000000000004,"code":"uba_user"},{"ID":3000000000039,"code":"ubs_audit"}]

Must be implemented in descendants and return (or resolved for async clients) to array of array representation of result, like this

 {"resultData":{"fields":["ID","name","ID.name"],"rowCount":1,"data":[[10,"admin","admin"]]},"total":1,"__totalRecCount": totolRecCountIfWithTotalRequest}

Must be implemented in descendants and return (or resolved for async clients) to DataSet class instance, implemented in caller level. It can be:

• {TubDataStore} for in-server context
• {UB.ux.data.UBStore} for UnityBase adminUI client
• array of array data representation for UnityBase remote connection
• etc.

Must be implemented in descendants as a alias to the most appropriate method

Apply miscellaneous options to resulting ubRequest:

     // this server-side call will select all currency, including deleted
     UB.Repository('cdn_currency').attrs(['ID']).misc({__allowSelectSafeDeleted: true}).selectAsArray();

Calculate total row number. WARNING!! This is VERY slow operation on DB level in case of many record

Result of calculation is returned in __totalRecCount parameter value in case selectAsArray() client call:

     var result = UB.Repository('uba_user').attrs(['ID', 'description']).withTotal().selectAsArray();
            console.log('Total count is:', result.__totalRecCount)

Or into TubDataStore.totalRowCount in case of server side selectAsStore() call:

     var store = UB.Repository('uba_user').attrs(['ID', 'description']).withTotal().selectAsStore();
            console.log('Total count is:', store.totalRowCount);