period in procedure name

Discussion of open issues, suggestions and bugs regarding LinqConnect – Devart's LINQ to SQL compatible ORM
Post Reply
alekas
Posts: 4
Joined: Thu 14 Feb 2013 19:34

period in procedure name

Post by alekas » Thu 14 Feb 2013 19:46

I have SQL procedure named
dbo.[XXX.YYY]

When I create a model and execute this procedure as a method of DataContext - the command sent to SQL server is this:

EXEC [dbo].[[XXX].[YYY]]

And of course it fails with SQL server message:
Msg 105, Level 15, State 1, Line 1
Unclosed quotation mark after the character string 'YYY]'.

Is there any way to make sure devart does not change the original procedure name from dbo.[XXX.YYY]
to
[dbo].[[XXX].[YYY]]
?

I have hundreds of procedures with "." in the name - it is a legacy from Oracle packages conversion ...

Any help?

Thanks,
Alex

MariiaI
Devart Team
Posts: 1472
Joined: Mon 13 Feb 2012 08:17

Re: period in procedure name

Post by MariiaI » Tue 19 Feb 2013 11:13

Thank you for the report. We have reproduced this issue. We will investigate it and inform you about the results as soon as possible.

MariiaI
Devart Team
Posts: 1472
Joined: Mon 13 Feb 2012 08:17

Re: period in procedure name

Post by MariiaI » Wed 20 Feb 2013 10:28

The bug with working with stored procedures named like "[XXX.XXX]" has been fixed. The fix will be included in the next build of LinqConnect. We will inform you when it is available for download.

Post Reply