1.2.7

Released: April 20, 2018

• [bug] [orm] Fixed regression in 1.2 within sharded query feature where the
  new "identity_token" element was not being correctly considered within
  the scope of a lazy load operation, when searching the identity map
  for a related many-to-one element. The new behavior will allow for
  making use of the "id_chooser" in order to determine the best identity
  key to retrieve from the identity map. In order to achieve this, some
  refactoring of 1.2's "identity_token" approach has made some slight changes
  to the implementation of ShardedQuery which should be noted for other
  derivations of this class.

  References: #4228

• [bug] [postgresql] Fixed bug where the special "not equals" operator for the PostgreSQL
  "range" datatypes such as DATERANGE would fail to render "IS NOT NULL" when
  compared to the Python None value.

  References: #4229

• [bug] [mssql] Fixed 1.2 regression caused by #4060 where the query used to
  reflect SQL Server cross-schema foreign keys was limiting the criteria
  incorrectly.

  References: #4234

• [bug] [oracle] The Oracle NUMBER datatype is reflected as INTEGER if the precision is NULL
  and the scale is zero, as this is how INTEGER values come back when
  reflected from Oracle's tables. Pull request courtesy Kent Bower.

• [feature] [postgresql] Added new PG type postgresql.REGCLASS which assists in casting
  table names to OID values. Pull request courtesy Sebastian Bank.

  References: #4160

• [bug] [sql] Fixed issue where the compilation of an INSERT statement with the
  "literal_binds" option that also uses an explicit sequence and "inline"
  generation, as on PostgreSQL and Oracle, would fail to accommodate the
  extra keyword argument within the sequence processing routine.

  References: #4231

• [bug] [orm] Fixed issue in single-inheritance loading where the use of an aliased
  entity against a single-inheritance subclass in conjunction with the
  Query.select_from() method would cause the SQL to be rendered with
  the unaliased table mixed in to the query, causing a cartesian product. In
  particular this was affecting the new "selectin" loader when used against a
  single-inheritance subclass.

  References: #4241