blocks|key|910559|text|Rails+4+ActiveRecord::Base不支持execute_procedure方法，尽管result+=+ActiveRecord::Base.connection仍然工作。即|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|910560|result+=+ActiveRecord::Base.connection.execute("call+example_proc('#{arg1}','#{arg2}')")|code-block|syntax|javascript|910561|entityMap^0|8|I|T|H|1F|12|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|L|$]]

Rails 4 <code>ActiveRecord::Base</code> doesn't support <code>execute_procedure</code> method, though <code>result = ActiveRecord::Base.connection</code> still works. ie 

<pre><code>result = ActiveRecord::Base.connection.execute("call example_proc('#{arg1}','#{arg2}')")
</code></pre>

blocks|key|637270|text|你可以试试下面的毗瑟奴方法|type|unstyled|depth|inlineStyleRanges|entityRanges|data|637271|或|637272|你也可以试试|637273|ActiveRecord::Base.connections.exec_query("call+example_proc('#{arg1}','#{arg2}')")|code-block|syntax|javascript|637274|这是文件|offset|length|637275|entityMap|0|LINK|mutability|MUTABLE|url|http://api.rubyonrails.org/classes/ActiveRecord/ConnectionAdapters/DatabaseStatements.html#method-i-exec_query^0|0|0|0|0|0|4|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@$M|11|N|12|1|13]]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

You can try Vishnu approach below

or 

You can also try

<pre><code>ActiveRecord::Base.connections.exec_query("call example_proc('#{arg1}','#{arg2}')")
</code></pre>

<a href="http://api.rubyonrails.org/classes/ActiveRecord/ConnectionAdapters/DatabaseStatements.html#method-i-exec_query" rel="nofollow">here is the document</a>

blocks|key|2061677|text|通常，您应该能够在常规的where或select方法中调用给定模型的存储过程：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2061678|YourModel.where("YOUR_PROC(?,+?)",+var1,+var2)|code-block|syntax|javascript|2061679|至于您的评论“我希望后面的过程验证是最正确的方法(对于警告和错误)”，我想这始终取决于您实际想要实现什么，以及您希望代码的可读性。|2061680|例如，如果您想返回YourModel属性的行，那么最好在where方法中使用上面的语句。另一方面，如果您编写了一些sql适配器，那么您可能希望降低到ActiveRecord::Base.connection.execute级别。|2061681|顺便说一句，这里应该提到一些关于存储proc性能的内容。在几个数据库中，数据库在存储proc的第一次运行时进行存储proc优化。但是，传递给第一次运行的参数可能是而不是，而不是稍后将更频繁地在其上运行的参数。因此，对于您的情况，存储的proc可能会以“无最优”的方式进行自动优化。这种情况可能会发生，也可能不会发生，但在使用带有动态参数的存储过程时，您应该考虑这一点。|BOLD|2061682|entityMap^0|C|5|I|6|0|0|0|S|5|0|29|3|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Z|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|13|8|@$9|14|A|15|B|Q]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|S|$]]

In general, you should be able to call stored procedures in a regular <code>where</code> or <code>select</code> method for a given model:

<pre><code>YourModel.where("YOUR_PROC(?, ?)", var1, var2)
</code></pre>

As for your comment "Bottom line I want the most correct approach with procedure validation afterwards (for warnings and errors)", I guess it always depends on what you actually want to implement and how readable you want your code to be.

For example, if you want to return rows of YourModel attributes, then it probably would be better if you use the above statement with <code>where</code> method. On the other hand, if you write some sql adapter then you might want to go down to the ActiveRecord::Base.connection.execute level.

BTW, there is something about stored proc performance that should be mentioned here. In several databases, database does stored proc optimization on the first run of the stored proc. However, the parameters that you pass to that first run might not be those that will be running on it more frequently later on. As a result, your stored-proc might be auto-optimized in a "none-optimal" way for your case. It may or may not happen this way, but it is something that you should consider while using stored procs with dynamic params.

blocks|key|910716|text|我相信您已经尝试过许多其他解决方案，并得到了一些或其他错误--主要是“不同步”或“关闭连接”错误。当您尝试执行查询时，每秒钟都会发生这些错误。我们需要像每次连接都是新的一样来解决这个问题。这是我的解决方案，没有抛出任何错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|910717|#checkout+a+connection+for+Model
conn+=+ModelName.connection_pool.checkout

#use+the+new+connection+to+execute+the+query
@records+=+conn.execute("call+proc_name('params')")

#checkout+the+connection
ModelName.connection_pool.checkin(conn)|code-block|syntax|javascript|910718|其他方法对我来说失败了，可能是因为ActiveRecord连接被自动处理，用于签出和检查每个线程。当我们的方法尝试签出一个连接只是为了执行SP时，它可能会发生冲突，因为只有在方法启动时才会有一个活动的连接。|910719|因此，这个想法是在工作完成后，手动#签出模型的连接，而不是从池中签出线程/函数和#签入。这对我很有用。|910720|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I believe you have tried many other solutions and got some or other errors mostly &quot;out of sync&quot; or &quot;closed connection&quot; errors. These errors occur every SECOND time you try to execute the queries. We need to workaround like the connection is new every time to overcome this. Here is my solution that didn't throw any errors.
<pre><code>#checkout a connection for Model
conn = ModelName.connection_pool.checkout

#use the new connection to execute the query
@records = conn.execute(&quot;call proc_name('params')&quot;)

#checkout the connection
ModelName.connection_pool.checkin(conn)
</code></pre>
The other approaches failed for me, possibly because ActiveRecord connections are automatically handled to checkout and checking for each thread. When our method tries to checkout a connection just to execute the SP, it might conflict since there will be an active connection just when the method started.
So the idea is to manually #checkout a connection for the model instead of for thread/function from the pool and #checkin once the work is done. This worked great for me.

There are few example out there but non of them are very clarified (or on old version).

I want to call MySQL procedure and check the return status (in rails <code>4.2</code>). The most common method I saw is to call <code>result = ActiveRecord::Base.connection.execute("call example_proc()")</code>, but in some places people wrote there is prepared method <code>result = ActiveRecord::Base.connection.execute_procedure("Stored Procedure Name", arg1, arg2)</code> (however it didn't compiled). 

So what is the correct way to call and get the status for MySQL procedure?

Edit:

And how to send parameters safly, where the first parameter is integer, second string and third boolean?

Calling MySQL stored procedure in ROR 4

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

没有几个例子，但其中没有非常明确(或在旧版本)。我想调用MySQL过程并检查返回状态(在rails 4.2中)。我看到的最常见的方法是调用result = ActiveRecord::Base.connection.execute("call example_proc()")，但是在一些地方，人们编写了准备方法resu...

问在ROR 4中调用MySQL存储过程
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在ROR 4中调用MySQL存储过程EN