SqlDataProvider does not have the functionality to specify schema of stored procedure (in contrast to accessing the tables). Rather, all stored procedures appear under ctx.Procedures where ctx is a database context obtained via call to GetDataContext, e.g.:
type private WorkerNodeDb = SqlDataProvider<
Common.DatabaseProviderTypes.MSSQLSERVER,
ConnectionString = WorkerNodeConnectionStringValue,
UseOptionTypes = Common.NullableColumnType.OPTION>
type private WorkerNodeDbContext = WorkerNodeDb.dataContext
let private getDbContext (c : unit -> ConnectionString) = c().value |> WorkerNodeDb.GetDataContext
This how clm.tryUpdateProgressRunQueue (from schema clm) appears in F#:
Hovering over (as shown on the picture) correctly shows that the stored procedure belongs to clm schema. This is inconvenient but that would've been OK and that could be dealt with.
However, the error appears if there is a stored procedure with the same name but in a different schema (eeInf in the example). The second procedure "acquires" an extra ' in the name:
Unfortunately, finally nothing works. Hovering over Invoke shows SP parameters mixed up from both procedures:
Here are the blank SPs along with schema creation scripts for convenience:
if not exists(select schema_name from information_schema.schemata where schema_name = 'clm') begin
print 'Creating schema clm...'
exec sp_executesql N'create schema clm'
end else begin
print 'Schema clm already exists...'
end
go
if not exists(select schema_name from information_schema.schemata where schema_name = 'eeInf') begin
print 'Creating schema eeInf...'
exec sp_executesql N'create schema eeInf'
end else begin
print 'Schema eeInf already exists...'
end
go
drop procedure if exists clm.tryUpdateProgressRunQueue
go
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
create procedure clm.tryUpdateProgressRunQueue (
@runQueueId uniqueidentifier,
@progress decimal(18, 14),
@callCount bigint,
@relativeInvariant float,
@maxEe float,
@maxAverageEe float,
@maxWeightedAverageAbsEe float,
@maxLastEe float)
as
begin
declare @rowCount int
set nocount on;
-- Do something useful here.
set @rowCount = @@rowcount
select @rowCount as [RowCount]
end
go
drop procedure if exists eeInf.tryUpdateProgressRunQueue
go
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
create procedure eeInf.tryUpdateProgressRunQueue (
@runQueueId uniqueidentifier,
@progress decimal(18, 14),
@callCount bigint,
@relativeInvariant float,
@dummy float)
as
begin
declare @rowCount int
set nocount on;
-- Do something useful here.
set @rowCount = @@rowcount
select @rowCount as [RowCount]
end
go
SqlDataProvider
does not have the functionality to specify schema of stored procedure (in contrast to accessing the tables). Rather, all stored procedures appear underctx.Procedures
wherectx
is a database context obtained via call toGetDataContext
, e.g.:This how
clm.tryUpdateProgressRunQueue
(from schemaclm
) appears in F#:Hovering over (as shown on the picture) correctly shows that the stored procedure belongs to
clm
schema. This is inconvenient but that would've been OK and that could be dealt with.However, the error appears if there is a stored procedure with the same name but in a different schema (
eeInf
in the example). The second procedure "acquires" an extra'
in the name:Unfortunately, finally nothing works. Hovering over
Invoke
shows SP parameters mixed up from both procedures:Here are the blank SPs along with schema creation scripts for convenience:
I am using SQLProvider version 1.3.7 and MSSQL.