-
The following API changes have been made in order to comply better with the X DevAPI:
-
Collection:Deprecated:
count().Changed:
getSchema()now returns aSchemainstance instead of the schema name. -
CollectionModify:Deprecated: Second parameter of
limit(x, y);arrayDelete(). -
CollectionFind:Deprecated: Second parameter of
limit(x, y).Added:
limit(x).offset(y). -
CollectionRemove:Deprecated: Second parameter of
limit(x, y). -
Table:Deprecated:
count()andinsert(Document)API.Updated:
getSchema()now returns aSchemainstance instead of the schema name.Removed:
as(). -
TableSelect:Deprecated: Second parameter of
limit(x, y).Added:
limit(x).offset(y). -
TableDelete:Deprecated: Second parameter of
limit(x, y);delete(x)in favor ofwhere(x). -
TableUpdate:Deprecated: Second parameter of
limit(x, y);update(x)in favor ofwhere(x). -
SqlExecute:Deprecated:
sqlExecute()in favor ofsql().Added:
bind(). -
Column:Added:
isNumberSigned(),getCollationName(),getCharacterSetName(), andisPadded().
(WL #11950)
-
The promise returned by the
session.sql().execute()method resolved to a plain JavaScript object rather than a properResultinstance. This meant that methods such asgetAffectedItemsCount()andgetWarnings()lacked access to the API. (Bug #28146988)Retrieving rows containing
NULLcolumns raised an unexpected assertion. (Bug #27978594)The
session.close()method is now asynchronous, returning a JavaScriptPromise, when before it simply returned immediately. (Bug #27893001)The right-padding mechanism was improved. (Bug #27839295, Bug #28275595, Bug #91503)
While calling
getSession()without arguments raises an Invalid parameter error, passing in {} raised Cannot read property 'length' of undefined. Now{}is supported, andgetSession()defaults to using an empty string as the user name. (Bug #27730748)Improved performance for expression parsing and protocol message encoding. (WL #11839, WL #11830)