Is your feature request related to a problem? Please describe.
The readme states this package supports a handful of adapters. But not SQL Server.
Expectations commonly result in selecting a True (validated) or False (failed) value. This is not how it's done in the SQL Server world, where booleans only exist in conditions and it is preferred to select 0 or 1 bits instead.
Describe the solution you'd like
Some macros need changes and a new dispatch target, sqlserver. We have already started work on this, resulting in most expectations being able to run in SQL Server, but we have not performed systematic testing of this yet.
Additional context
This is probably related to Fabric support as well.
Additional points of discussion
How complete does a solution need to be to be merged as a complete new adapter? Is it possible to start with only partial SQL Server support?
Is your feature request related to a problem? Please describe.
The readme states this package supports a handful of adapters. But not SQL Server.
Expectations commonly result in selecting a True (validated) or False (failed) value. This is not how it's done in the SQL Server world, where booleans only exist in conditions and it is preferred to select 0 or 1 bits instead.
Describe the solution you'd like
Some macros need changes and a new dispatch target, sqlserver. We have already started work on this, resulting in most expectations being able to run in SQL Server, but we have not performed systematic testing of this yet.
Additional context
This is probably related to Fabric support as well.
Additional points of discussion
How complete does a solution need to be to be merged as a complete new adapter? Is it possible to start with only partial SQL Server support?