Array literals are now rendered as ARRAY[3,4]::integer[], including
explicit typing. This fixes:
1. Empty array literals (ARRAY[] raised an error).
2. Cases such as arrays of shorts, which would render as ARRAY[3,4]
   and which PostgreSQL would take to be an array of ints.

Fixes #439

No operation translation yet

Closes #392

* Multidimensional arrays not yet supported (#314)
* In some cases boxing will occur when comparing (and snapshotting) the
  elements (https://github.com/aspnet/EntityFrameworkCore/issues/11072)

Closes #305

Switch to dotnet-core feed

Closes #339

This reverts commit dfdc3364.

Pending resolution of
https://github.com/aspnet/EntityFrameworkCore/issues/11077

* Multidimensional arrays not yet supported (#314)
* In some cases boxing will occur when comparing (and snapshotting) the
  elements (https://github.com/aspnet/EntityFrameworkCore/issues/11072)

Closes #305

After store type name change

* Moved to new 2.1 type mapper interface
* Switched to simple hardcoded mapping creation rather than attempting
  to dynamically load them from ADO, which made no sense as we need
  literal generation anyway.
* Added many mappings with the literal translations, not complete.

Array indexing, length, SequenceEqual, Contains

Closes #120

Fixes #205

Does not include scaffolding

Work on #15

Fixes #18

Note that no tests have been executed and the provider is probably still
broken in some ways (this is just a first step).

Fixes #17

From commit bb43e2282fb13b0deb931d199c95d07ab84169a0.
Project does not compile.