blocks|key|3831228|text|根本没有办法在飞行中做到这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3831229|您需要更改默认连接，以便将其雄辩地用于渴望加载的模型。您可以将它包装在下面这样的帮助器方法中：|3831230|function+on($connection,+Closure+$callback)
{
++++//+backup+default+connection
++++$default+=+Config::get('database.default');

++++//+change+for+current+query
++++Config::set('database.default',+$connection);

++++//+run+the+query
++++$result+=+$callback();

++++//+restore+the+default+connection
++++Config::set('database.default',+$default);

++++return+$result;
}|code-block|syntax|javascript|3831231|然后打个电话，如下所示：|3831232|$models+=+on('secondary_connection',+function+()+{
+++return+MyModel::with('relation')->get();
});|3831233|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

There's literally no way to do it on the fly.

You need to alter the default connection in order to make Eloquent use it for the eager loaded models. You can wrap it in a helper method like this:

<pre><code>function on($connection, Closure $callback)
{
 // backup default connection
 $default = Config::get('database.default');

 // change for current query
 Config::set('database.default', $connection);

 // run the query
 $result = $callback();

 // restore the default connection
 Config::set('database.default', $default);

 return $result;
}
</code></pre>

then just call like below:

<pre><code>$models = on('secondary_connection', function () {
 return MyModel::with('relation')-&gt;get();
});
</code></pre>

blocks|key|1006297|text|嗯，正如许多用户所建议的那样，似乎没有办法在飞行中做到这一点。我对此的理解是，当涉及到管理多个连接时，雄辩是不完整的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1006298|我想有两种方法可以解决这个问题。|1006299|首先，在模型中指定连接：|1006300|class+MyModel+{
++++$protected+connection+=+'secondary_connection';
}|code-block|syntax|javascript|1006301|这显然是一个糟糕的解决办法，因为这个模型只能在一个连接中使用.但仍然有效。|1006302|然后，正如Jarek所建议的那样，可以使用新的连接来切换default连接。但是，与其在配置文件中执行此操作，还可以交换PDO对象。|1006303|++++$default+=+DB::getPdo();+//+Default+conn
++++$secondary+=+DB::connection('secondary_connection')->getPdo();
++++DB::setPdo($secondary);
++++$result+=+MyModel::with('AnotherModel')->get();
++++DB::setPdo($default);|1006304|这是一个可行的解决办法，可以是一个干净的解决方案。下一步是把开关机构在一个很好的拉拉维尔方式。|1006305|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|H|7|10|8|@]|9|@]|A|$I|J]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Well, as I've been suggested by many users, it seems that there's no way to do this on the fly. My understanding of this is that Eloquent is incomplete when comes to manage multi-connection.
There's 2 way to work this around I could figure.
First, specify the connection in the model :
<pre><code>class MyModel {
 $protected connection = 'secondary_connection';
}
</code></pre>
That is obviously a bad workaround since this model is only usable in one connection... but still works.
Then, as Jarek Tkaczyk suggested, it is possible to switch de default connection with the new one. But instead of doing it in the config file, it is possible to swap the PDO oject.
<pre><code> $default = DB::getPdo(); // Default conn
 $secondary = DB::connection('secondary_connection')-&gt;getPdo();
 DB::setPdo($secondary);
 $result = MyModel::with('AnotherModel')-&gt;get();
 DB::setPdo($default);
</code></pre>
That is a workaround that works and can be a clean solution. Next step is to put that switching mechanism in a nice Laravel way.

blocks|key|1006318|text|最后，我将简单的关系函数替换为更多的自定义函数。例如，我的->relatedModel在某种程度上是雄辩模型中原始版本的副本，但包括设置连接：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1006319|public+function+relatedModel()+{
++$instance+=+new+\relatedModel;
++$instance->setConnection($this->getConnectionName());
++$query+=+$instance->newQuery();

++return+new+BelongsTo($query,+$this,+'myForeignKey',+$instance->getKeyName(),+null);
}|code-block|syntax|javascript|1006320|我在拉拉维尔5号，所以这可能和4.2不一样。|1006321|由于我在处理这个问题，所以这里有一种很好的方法来完成对另一个连接的验证，而不是默认的连接：http://laravel.io/forum/10-29-2014-validation-rules-and-multiple-db-connections。|1006322|如果它是一个模型方法，您甚至可以将其缩短为：|1006323|$v+=+Validator::make($data,+$rules);
$v->getPresenceVerifier()->setConnection($this->getConnectionName());|1006324|entityMap|0|LINK|mutability|MUTABLE|url|http://laravel.io/forum/10-29-2014-validation-rules-and-multiple-db-connections^0|T|E|0|0|0|19|27|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|14|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|15|8|@]|D|@$9|16|A|17|1|18]]|E|$]]|$1|O|3|P|5|6|7|19|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1A|8|@]|D|@]|E|$I|J]]|$1|S|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]]]

I ended up with replacing the simply relationship functions with a bit more custom onces. For instance my <code>-&gt;relatedModel</code> is somewhat of a copy of the original in the Eloquent Model, but includes setting the connection:

<pre class="lang-php prettyprint-override"><code>public function relatedModel() {
 $instance = new \relatedModel;
 $instance-&gt;setConnection($this-&gt;getConnectionName());
 $query = $instance-&gt;newQuery();

 return new BelongsTo($query, $this, 'myForeignKey', $instance-&gt;getKeyName(), null);
}
</code></pre>



I'm on Laravel 5, so maybe this is different to 4.2.

And since I was fiddling around with this issue a lot now here is a great way to get Validation done over another connection than the default: <a href="http://laravel.io/forum/10-29-2014-validation-rules-and-multiple-db-connections" rel="nofollow">http://laravel.io/forum/10-29-2014-validation-rules-and-multiple-db-connections</a>

If it is a model method, you can even shorten it down to:

<pre class="lang-php prettyprint-override"><code>$v = Validator::make($data, $rules);
$v-&gt;getPresenceVerifier()-&gt;setConnection($this-&gt;getConnectionName());
</code></pre>

blocks|key|1501469|text|我也在处理这个问题。我找到了一个解决方案，但只有在通过.env文件配置所使用的连接是可以接受的情况下，它才能工作。如果您想动态地更改它，这是行不通的，尽管在这种情况下，您可以使用一些逻辑(调用函数)来返回正确的连接名。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1501470|我的解决方案是重写模型类的connectionName方法。在我的例子中，我为我的所有模型提供了一个基类来处理这个问题：|1501471|abstract+class+ModelBase+extends+Model
{
++++public+function+getConnectionName()
++++{
++++++++return+env('ELOQUENT_DB_CONNECTION',+parent::getConnectionName());
++++}
}|code-block|syntax|javascript|1501472|正如我所提到的，您可以在getConnectionName中放置任何您想要的逻辑，这样您就可以使它更加动态。|1501473|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I also am dealing with this issue. I found a solution but it will only work if it is acceptable to configure the used connection through the .env file. This will not work if you want to change it dynamically although you could in that case use a bit of logic (call a function) to return the correct connection name.

The solution I have is to override the connectionName method of the Model class. In my case I have a base class for all my models that takes care of this:

<pre><code>abstract class ModelBase extends Model
{
 public function getConnectionName()
 {
 return env('ELOQUENT_DB_CONNECTION', parent::getConnectionName());
 }
}
</code></pre>

As I mentioned you can put whatever logic you want in the getConnectionName so you can make it more dynamic.

blocks|key|1006393|text|class+MyModel+{
++++$protected+connection+=+'secondary_connection';
}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1006394|是不错的选择，因为雄辩的模型是DB正面%2B附加。所有DB外观功能也适用于雄辩的模型。因此，与更改db+facade中的连接不同，我们可以在这里更改它，但没有区别。|unstyled|1006395|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>class MyModel {
 $protected connection = 'secondary_connection';
}
</code></pre>

is the nice option as eloquent models are DB facades + extras. all DB facades functions also apply to eloquent models. therefore instead of changing connection in db facade we can change it here only there is no difference.

I am trying to use Laravel Eloquent ORM to do a simple one to one relationship on two different connections.
Let say I do :
<pre><code>MyModel::on('secondary_connection')-&gt;get()
</code></pre>
That is working fine.
When I do :
<pre><code>MyModel::on('secondary_connection')-&gt;with('AnotherModel')-&gt;get();
</code></pre>
I am getting an error because eloquent is doing the AnotherModel SELECT statement on the default connection (instead of &quot;secondary_connection&quot;).
I can't find a way to work this around.
My models are well defined since I can join them in my default connection.
Thoughts ?

Laravel Eloquent eager loading on a different connection

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我试图用Laravel雄辩的ORM在两种不同的联系上做一个简单的一对一的关系。让我这么说吧：MyModel::on('secondary_connection')->get()效果很好。当我这么做时：MyModel::on('secondary_connection')->with('AnotherModel')->g...

问拉勒维尔雄辩地热切地加载着另一种连接
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问拉勒维尔雄辩地热切地加载着另一种连接EN