旧的无法切换/更改/切换ALTER PROCEDURE< ---> CREATE PROCEDURE错误（或者它是一个功能？） [英] The old inability to toggle/change/switch between ALTER PROCEDURE <---> CREATE PROCEDURE bug (or is it a feature?)
问题描述
请记住这是我的第一个编译的SQL程序存储过程
（SP），从Visual Studio中的Frasier Visual C ++ .NET书中复制
2005（ Chap12）。到目前为止，所以理论，除了一个bug（功能？）
以下。在某些时候，我肯定我能够笑到这一点，类似于在C / C ++中伪造一个分号，但是现在它令人沮丧
（暂时睡上一段时间）。
问题 -
由于某种原因，我在尝试保存时遇到错误文件中两个
表（称为作者和内容），由一个键链接，形成一个
的关系。
By简单比较教科书和我的程序中的源代码
（下面）我发现了差异：而不是像教科书中那样，
存储过程（SP）从CREATE PROCEDURE开始，它自动*是*（以某种方式）给出''ALTER PROCEDURE''的名称
我无法将其更改为 ; CREATE PROCEDURE （你在MS中得到一个错误
XXX的对象，见下面的* | *）。无论我做什么，SP都会被Visual Studio 2005改为改变程序!!!
（否则它根本不会保存）
其他人有这种情况吗？ （见下文，其他人已经发生这种情况
多年来，但目前尚不清楚解决方法是什么）
请记住这是我的第一次尝试，我已经订购了一些关于SQL的专业书籍，但如果这是一个常见的问题（而且我怀疑它是某种bug或怪癖） VS2005），请告诉我。
坦率地说，我觉得VS2005做的SQL搞砸了。
这里有两个Usenet线程这个问题：
（1） http：// tinyurl。 com / 2o956m 或，
http://groups.google.com/group/micro ...... 454182ae77d409
（2） http://tinyurl.com/2ovybv 或，
http://groups.google.com/group/micro...e5428bf0525889
第二个帖子暗示这是一个错误 - 任何修复？
此错误也可能与我成功更改后已从管理员切换到PowerUser的事实（而不是
重新启动）相关
SQL Server Management Studio Express中的权限（请参阅此
线程： http://tinyurl.com/2o5yqa ）
关于这个问题，我可能会再试一次，看看是否重启
帮助。
BTW，如果我不能让这个工作，那是什么我的SQL编辑器/
编译器我应该使用MS Visual Studio 2005 for ADO.NET和
SQL dB开发吗？
RL
//源文件
//错误信息：
''作者''表保存成功
''内容''表
- 无法创建关系''FK_Content_Authors''。
ALTER TABLE语句与FOREIGN KEY冲突约束
FK_Content_Authors。冲突发生在数据库DCV_DB，
表dbo.Authors，列''AuthorID''。
//由于毫无疑问！
-
创建程序dbo.InsertAuthor / *这是正确的（我想要的）
' '创建程序''不''更改程序''* /
（
@ LastName NVARCHAR（32）= NULL，
@FirstName NVARCHAR（32）= NULL
）
AS
/ * SET NOCOUNT ON * /
INSERT INTO作者（姓氏，名字）
VALUES（@姓氏，@ FirstName）
返回
-
ALTER PROCEDURE dbo.InsertAuthor / *错误！我想''创建程序''
不是''ALTER PROCEDURE''但是VS2005不会这样保存!!! * /
（
@LastName NVARCHAR（32）= NULL，
@FirstName NVARCHAR（32）= NULL
）
AS
/ * SET NOCOUNT ON * /
INSERT INTO作者（LastName，FirstName）
VALUES（@ LastName，@ FirstName）
返回
-
* | *出现错误信息：当试图保存CREATE PROCEDURE存储
过程：在dB中已经有一个名为''InsertAuthor''的对象
看起来你很困惑通过执行proc创建proc。 MV显然会显示（当你选择编辑或类似的东西时，你会选择编辑或类似的东西），开始时使用ALTER PROC的proc代码，假设你想要修改源代码的
程序。
与从IDE开发C app相比。 IDE允许您使用源代码。这是
ALTER PROC部分。当您打开/编辑或VS中的任何proc时，它会从系统表中读取
proc的源代码，并将初始CREATE替换为ALTER，假设您要修改
源代码。
执行C代码不同于编译和链接它。
对于您引用的第一个URL ，我们从来没有得到实际发生的事情的责备。对于
秒，我们发现了一个错误，工具错误地不仅将CREATE PROC更改为ALTER PROC，而且
也改变了proc *中的代码*，例如CREATE TABLE更改为ALTER TABLE。
另外，我建议您将源代码保存在文件中，允许您对它们进行版本化（源安全
等）。或者甚至看看Visual Studio for Database Professionals。
-
Tibor Karaszi，SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
" raylopez99" < ra ******** @ yahoo.comwrote in message
news：11 ********************** @ p15g2000hsd.googlegr oups.com ...
请记住这是我的第一个编译的SQL程序存储过程
（SP），在Visual Studio中通过Frasier Visual C ++ .NET从书中复制
2005（第12章）。到目前为止，所以理论，除了一个bug（功能？）
以下。在某些时候，我肯定我能够笑到这一点，类似于在C / C ++中伪造一个分号，但是现在它令人沮丧
（暂时睡上一段时间）。
问题 -
由于某种原因，我在尝试保存时遇到错误文件中两个
表（称为作者和内容），由一个键链接，形成一个
的关系。
By简单比较教科书和我的程序中的源代码
（下面）我发现了差异：而不是像教科书中那样，
存储过程（SP）从CREATE PROCEDURE开始，它自动*是*（以某种方式）给出''ALTER PROCEDURE''的名称
我无法将其更改为 ; CREATE PROCEDURE （你在MS中得到一个错误
XXX的对象，见下面的* | *）。无论我做什么，SP都会被Visual Studio 2005改为改变程序!!!
（否则它根本不会保存）
其他人有这种情况吗？ （见下文，其他人已经发生这种情况
多年来，但目前尚不清楚解决方法是什么）
请记住这是我的第一次尝试，我已经订购了一些关于SQL的专业书籍，但如果这是一个常见的问题（而且我怀疑它是某种bug或怪癖） VS2005），请告诉我。
坦率地说，我觉得VS2005做的SQL搞砸了。
这里有两个Usenet线程这个问题：
（1） http：// tinyurl。 com / 2o956m 或，
http://groups.google.com/group/micro ...... 454182ae77d409
（2） http://tinyurl.com/2ovybv 或
http://groups.google.com/group/micro...e5428bf0525889
第二个线程暗示这是一个错误 - 任何修复？
此错误也可能与我成功更改后已从管理员切换到PowerUser的事实（而不是
重启）
SQL Server Management Studio Express中的权限（请参阅此
主题： http ：//tinyurl.com/2o5yqa ）
关于这个问题，我可能会再试一次，看看是否重启
有帮助。
顺便说一句，如果我不能让它工作，还有其他SQL edi除了MS Visual Studio 2005 for ADO.NET和
SQL dB开发之外我应该使用
编译器吗？
RL
//源文件
//错误信息：
''作者''表保存成功
''内容''表
- 无法创建关系''FK_Content_Authors''。
ALTER TABLE语句与FOREIGN KEY约束
" FK_Content_Authors" ;.冲突发生在数据库DCV_DB，
表dbo.Authors，列''AuthorID''。
//由于毫无疑问！
-
创建程序dbo.InsertAuthor / *这是正确的（我想要的）
' '创建程序''不''更改程序''* /
（
@ LastName NVARCHAR（32）= NULL，
@FirstName NVARCHAR（32）= NULL
）
AS
/ * SET NOCOUNT ON * /
INSERT INTO作者（姓氏，名字）
VALUES（@姓氏，@ FirstName）
返回
-
ALTER PROCEDURE dbo.InsertAuthor / *错误！我想''创建程序''
不是''ALTER PROCEDURE''但是VS2005不会这样保存!!! * /
（
@LastName NVARCHAR（32）= NULL，
@FirstName NVARCHAR（32）= NULL
）
AS
/ * SET NOCOUNT ON * /
INSERT INTO作者（LastName，FirstName）
VALUES（@ LastName，@ FirstName）
返回
-
* | *出现错误信息：当试图保存CREATE PROCEDURE存储
过程：已经有一个名为''InsertAuthor''的对象在dB
raylopez99（ra ******** @ yahoo.com）写道：
//错误信息：
''作者'表已成功保存
''内容''表
- 无法创建关系''FK_Content_Authors''。
ALTER TABLE语句与FOREIGN KEY缺点冲突traint
" FK_Content_Authors"。冲突发生在数据库DCV_DB，
表dbo.Authors，列''AuthorID''。
//由于毫无疑问！
-
创建程序dbo.InsertAuthor / *这是正确的（我想要的）
' 'CREATE PROCEDURE''''''ALTER PROCEDURE''* /
不！那与它无关！在上面，您尝试将一个
外键从Content表添加到Authors表，但是有
数据可以防止这种情况发生。也许是因为在尝试应用外键之前，您已经在内容中输入了
。这个
与你的程序完全无关。
这是一个演示的脚本：
CREATE TABLE作者（
authorid int NOT NULL，
name nvarchar（50）NOT NULL，
CONSTRAINT pk_authors PRIMARY KEY（authorid））
go
- 非常简单的书桌。我忽略了ISBN和
这一事实 - 一本书可以有几位作者。
CREATE TABLE书籍（
bookid int NOT NULL，
title nvarchar（1000）NOT NULL，
authorid int NOT NULL，
CONSTRAINT pk_books PRIMARY KEY（bookid））
go
- 在我们添加任何作者之前，我们急切地插入一本书。
INSERT书籍（bookid，title，authorid）
VALUES（1，'The Mouse Trap''，1）
go
- 哎呀，有人告诉我们外键是个好主意。 />
ALTER TABLE书籍ADD
CONSTRAINT fk_books_authors FOREIGN KEY（authorid）
参考作者（作者）
go
- 失败了。我们必须首先添加作者：
INSERT作者（作者，姓名）
VALUES（1，'''Agatha Christie''）
go
- 现在应该可以工作了。
ALTER TABLE书籍ADD
CONSTRAINT fk_books_authors FOREIGN KEY（authorid）
参考文献作者（作者）
go
- 清理。
DROP TABLE书籍，作者
请注意这是所有SQL命令。虽然点击式表格设计的GUI可以让你在没有经验的情况下更快地工作，但是如果你计划的话，学习SQL命令绝对是必不可少的。 />
SQL编程专业生涯。一旦你很好地了解命令，
如果你发现更方便，你可以使用GUI工具。但是所有
工具所做的就是生成如上所述的命令，而且没有知识
并且了解这一点，当出现问题时你会非常无能为力。
-
Erland Sommarskog，SQL Server MVP， es **** @ sommarskog.se
SQL Server 2005联机丛书
http://www.microsoft.com/technet/pro...ads/books.mspx
书籍在线获取SQL Server 2000
http：// www.microsoft.com/sql/prodinf...ons/books.mspx
4月1日凌晨3:22，Erland Sommarskog< esq ... @ sommarskog.sewrote：
>
注意这是所有SQL命令的方式。虽然点击式表格设计的GUI可以让你在没有经验的情况下更快地工作，但是如果你计划的话，学习SQL命令绝对是必不可少的。 />
SQL编程专业生涯。一旦你很好地了解命令，
如果你发现更方便，你可以使用GUI工具。但是所有
工具所做的就是生成如上所述的命令，而且没有知识
并且了解这一点，当出现问题时你会非常无能为力。
-
Erland Sommarskog，SQL Server MVP，esq ... @ sommarskog.se
联机丛书SQL Server 2005 http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books ...
SQL Server 2000联机丛书http://www.microsoft.com/ sql / prodinfo / previousversions / books.mspx
感谢Erland - 我已将您的示例添加为书签以供将来参考，
我订购的SQL书籍。现在我正在努力学习
了解SQL编辑器和IDE的工作原理。由于一些奇怪的原因，我是能够保存同样的例子虽然是管理员，而不是
PowerUser，但我认为这只是巧合 - 我必须插入一个
错误的单词或一些错误的语义PowerUser版本，
保存在自己独立的数据库中。权限似乎是一个大问题
与现代SQL数据库BTW - 最终我希望弄清楚如何使用命令动态操作权限
，你似乎在另一个帖子中显示
。
似乎SQL就像是一种自上而下的宏语言。程序性
当然不是面向对象的。
现在进入我的SQL GUI中的下一个主题数字书：
连接vs断开连接ADO.NET（我为了好玩而编程，而不是专业的
）。
RL
Keep in mind this is my first compiled SQL program Stored Procedure
(SP), copied from a book by Frasier Visual C++.NET in Visual Studio
2005 (Chap12). So far, so theory, except for one bug (feature?)
below. At some point I''m sure I''ll be able to laugh about this, akin
to forgeting a semi-colon in C/C++, but right now it''s frustrating
(time to sleep on it for a while).
Problem--
For some reason I get the error when trying to save files where two
tables (called Author and Content), linked by a single key, form a
relationship.
By simple comparison of the source code in the textbook and my program
(below) I found the difference: instead of, like in the textbook, the
Stored Procedure (SP) starting with "CREATE PROCEDURE", it
*automatically* is (was somehow) given the name of ''ALTER PROCEDURE''
and I cannot change this to "CREATE PROCEDURE" (you get an error in MS
Visual Studio 2005 Pro edition of "There is already an object named
XXX in the database", see *|* below). No matter what I do, the SP is
always changed by Visual Studio 2005 to ''ALTER PROCEDURE''!!!
(otherwise it simply will not save)
Anybody else have this happen? (See below, others have had this happen
over the years but it''s not clear what the workaround is)
Keep in mind this is my first attempt and I have ordered some
specialized books on SQL, but if this is a common problem (and I
suspect it''s some sort of bug or quirk in VS2005), please let me know.
Frankly I think SQL as done by VS2005 is messed up.
Here are two Usenet threads on this problem:
(1) http://tinyurl.com/2o956m or,
http://groups.google.com/group/micro...454182ae77d409
(2) http://tinyurl.com/2ovybv or,
http://groups.google.com/group/micro...e5428bf0525889
The second thread implies this is a bug--any fix?
Also this bug might be relate to the fact I''ve switched (and not
rebooted) from Administrator to PowerUser after successfully changing
the permissions in the SQL Server Management Studio Express (see this
thread: http://tinyurl.com/2o5yqa )
Regarding this problem I might try again tommorrow to see if rebooting
helps.
BTW, in the event I can''t get this to work, what other SQL editor/
compiler should I use besides MS Visual Studio 2005 for ADO.NET and
SQL dB development?
RL
// source files
// error message:
''Authors'' table saved successfully
''Content'' table
- Unable to create relationship ''FK_Content_Authors''.
The ALTER TABLE statement conflicted with the FOREIGN KEY constraint
"FK_Content_Authors". The conflict occurred in database "DCV_DB",
table "dbo.Authors", column ''AuthorID''.
// due to the below no doubt!
--
CREATE PROCEDURE dbo.InsertAuthor /* THIS IS CORRECT (what I want)
''CREATE PROCEDURE'' not ''ALTER PROCEDURE''*/
(
@LastName NVARCHAR(32) = NULL,
@FirstName NVARCHAR(32) = NULL
)
AS
/* SET NOCOUNT ON */
INSERT INTO Authors (LastName, FirstName)
VALUES (@LastName, @FirstName)
RETURN
--
ALTER PROCEDURE dbo.InsertAuthor /* WRONG! I want ''CREATE PROCEDURE''
not ''ALTER PROCEDURE'' but VS2005 won''t save it as such!!!*/
(
@LastName NVARCHAR(32) = NULL,
@FirstName NVARCHAR(32) = NULL
)
AS
/* SET NOCOUNT ON */
INSERT INTO Authors (LastName, FirstName)
VALUES (@LastName, @FirstName)
RETURN
--
*|* Error message given: when trying to save CREATE PROCEDURE Stored
Procedure: "There is already an object named ''InsertAuthor'' in the dB
It seems you are confusing creating the proc with executing the proc. MV apparently displays (when
you select Edit or something similar), the proc code with an ALTER PROC in the beginning, assuming
that you want to modify the source code for the procedure.
Compare to developing a C app from an IDE. The IDE let you work with the source code. This is the
ALTER PROC part. When you open/edit or whatever the proc in VS, it reads the source code for the
proc from the system tables and replace the initial CREATE to ALTER assuming that you want to modify
the source code.
Executing the C code is different from compiling and linking it.
For the first URL you referred to, we never got a repro of what actually was happening. For the
second, we found a bug where the tool incorrectly not only changed CREATE PROC to ALTER PROC, but
also code *inside the proc* was changed such as CREATE TABLE changed to ALTER TABLE.
Also, I suggest you keep your source code in files, which allow you to version them (Source safe
etc). Or even look at Visual Studio for Database Professionals.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"raylopez99" <ra********@yahoo.comwrote in message
news:11**********************@p15g2000hsd.googlegr oups.com...Keep in mind this is my first compiled SQL program Stored Procedure
(SP), copied from a book by Frasier Visual C++.NET in Visual Studio
2005 (Chap12). So far, so theory, except for one bug (feature?)
below. At some point I''m sure I''ll be able to laugh about this, akin
to forgeting a semi-colon in C/C++, but right now it''s frustrating
(time to sleep on it for a while).
Problem--
For some reason I get the error when trying to save files where two
tables (called Author and Content), linked by a single key, form a
relationship.
By simple comparison of the source code in the textbook and my program
(below) I found the difference: instead of, like in the textbook, the
Stored Procedure (SP) starting with "CREATE PROCEDURE", it
*automatically* is (was somehow) given the name of ''ALTER PROCEDURE''
and I cannot change this to "CREATE PROCEDURE" (you get an error in MS
Visual Studio 2005 Pro edition of "There is already an object named
XXX in the database", see *|* below). No matter what I do, the SP is
always changed by Visual Studio 2005 to ''ALTER PROCEDURE''!!!
(otherwise it simply will not save)
Anybody else have this happen? (See below, others have had this happen
over the years but it''s not clear what the workaround is)
Keep in mind this is my first attempt and I have ordered some
specialized books on SQL, but if this is a common problem (and I
suspect it''s some sort of bug or quirk in VS2005), please let me know.
Frankly I think SQL as done by VS2005 is messed up.
Here are two Usenet threads on this problem:
(1) http://tinyurl.com/2o956m or,
http://groups.google.com/group/micro...454182ae77d409
(2) http://tinyurl.com/2ovybv or,
http://groups.google.com/group/micro...e5428bf0525889
The second thread implies this is a bug--any fix?
Also this bug might be relate to the fact I''ve switched (and not
rebooted) from Administrator to PowerUser after successfully changing
the permissions in the SQL Server Management Studio Express (see this
thread: http://tinyurl.com/2o5yqa )
Regarding this problem I might try again tommorrow to see if rebooting
helps.
BTW, in the event I can''t get this to work, what other SQL editor/
compiler should I use besides MS Visual Studio 2005 for ADO.NET and
SQL dB development?
RL
// source files
// error message:
''Authors'' table saved successfully
''Content'' table
- Unable to create relationship ''FK_Content_Authors''.
The ALTER TABLE statement conflicted with the FOREIGN KEY constraint
"FK_Content_Authors". The conflict occurred in database "DCV_DB",
table "dbo.Authors", column ''AuthorID''.
// due to the below no doubt!
--
CREATE PROCEDURE dbo.InsertAuthor /* THIS IS CORRECT (what I want)
''CREATE PROCEDURE'' not ''ALTER PROCEDURE''*/
(
@LastName NVARCHAR(32) = NULL,
@FirstName NVARCHAR(32) = NULL
)
AS
/* SET NOCOUNT ON */
INSERT INTO Authors (LastName, FirstName)
VALUES (@LastName, @FirstName)
RETURN
--
ALTER PROCEDURE dbo.InsertAuthor /* WRONG! I want ''CREATE PROCEDURE''
not ''ALTER PROCEDURE'' but VS2005 won''t save it as such!!!*/
(
@LastName NVARCHAR(32) = NULL,
@FirstName NVARCHAR(32) = NULL
)
AS
/* SET NOCOUNT ON */
INSERT INTO Authors (LastName, FirstName)
VALUES (@LastName, @FirstName)
RETURN
--
*|* Error message given: when trying to save CREATE PROCEDURE Stored
Procedure: "There is already an object named ''InsertAuthor'' in the dB
raylopez99 (ra********@yahoo.com) writes:// error message:
''Authors'' table saved successfully
''Content'' table
- Unable to create relationship ''FK_Content_Authors''.
The ALTER TABLE statement conflicted with the FOREIGN KEY constraint
"FK_Content_Authors". The conflict occurred in database "DCV_DB",
table "dbo.Authors", column ''AuthorID''.
// due to the below no doubt!
--
CREATE PROCEDURE dbo.InsertAuthor /* THIS IS CORRECT (what I want)
''CREATE PROCEDURE'' not ''ALTER PROCEDURE''*/No! That has nothing to do with it! In the above you are try to add a
foreign key from the Content table to the Authors table, but there is
data that prevents this from happening. Maybe because you had already
entered data in Contents before you tried to apply the foreign key. This
is entirely unrelated to your procedure.
Here is a script that demontstrates:
CREATE TABLE Authors (
authorid int NOT NULL,
name nvarchar(50) NOT NULL,
CONSTRAINT pk_authors PRIMARY KEY (authorid))
go
-- Very simple book table. I ignore ISBN and the fact that
-- a book can have several authors.
CREATE TABLE Books (
bookid int NOT NULL,
title nvarchar(1000) NOT NULL,
authorid int NOT NULL,
CONSTRAINT pk_books PRIMARY KEY (bookid))
go
-- Being eager, we insert a book, before we add any authors.
INSERT Books (bookid, title, authorid)
VALUES(1, ''The Mouse Trap'', 1)
go
-- Oops, someone told us that foreign keys is a good idea.
ALTER TABLE Books ADD
CONSTRAINT fk_books_authors FOREIGN KEY (authorid)
REFERENCES Authors(authorid)
go
-- It failed. We must add the author first:
INSERT Authors (authorid, name)
VALUES (1, ''Agatha Christie'')
go
-- It should work now.
ALTER TABLE Books ADD
CONSTRAINT fk_books_authors FOREIGN KEY(authorid)
REFERENCES Authors(authorid)
go
-- Clean up.
DROP TABLE Books, Authors
Note by the way that this is all SQL commands. While point-and-click
GUIs for table design can make you work faster if you are unexperienced,
learning the SQL commands is absolutely essential if you plan for a
professional career in SQL programming. Once you know the commands well,
you can use GUI tools if you find that more convenient. But all the
tools do is to generate the commands like the above, and without knowledge
and understanding of that, you are pretty clueless when things go wrong.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
On Apr 1, 3:22 am, Erland Sommarskog <esq...@sommarskog.sewrote:
>
Note by the way that this is all SQL commands. While point-and-click
GUIs for table design can make you work faster if you are unexperienced,
learning the SQL commands is absolutely essential if you plan for a
professional career in SQL programming. Once you know the commands well,
you can use GUI tools if you find that more convenient. But all the
tools do is to generate the commands like the above, and without knowledge
and understanding of that, you are pretty clueless when things go wrong.
--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspxThanks Erland--I have bookmarked your example for future reference,
after I read some SQL books I ordered. Right now I''m trying to just
learn how the SQL editor and IDE work. For some strange reason I was
able to "save" the same example while as Administrator rather than
PowerUser, but I think it''s just a coincidence--I must have inserted a
wrong word or some wrong semantics in the PowerUser version, which is
kept in its own seperate database. Permissions seems to be a big deal
with modern SQL databases BTW--eventually I hope to figure out how to
manipulate permissions on the fly with commands, as you seemed to show
in another thread.
Seems like SQL is like a macro language that is "top-down" procedural
and definitely not object oriented of course.
Now onto the next topic in my SQL GUI paint-by-numbers book:
connected vs disconnected ADO.NET (I program for fun, not
professionally).
RL
这篇关于旧的无法切换/更改/切换ALTER PROCEDURE< ---> CREATE PROCEDURE错误（或者它是一个功能？）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
