This repository was archived by the owner on Sep 16, 2021. It is now read-only.
File tree Expand file tree Collapse file tree 1 file changed +8
-1
lines changed Expand file tree Collapse file tree 1 file changed +8
-1
lines changed Original file line number Diff line number Diff line change @@ -162,6 +162,8 @@ Once you set up Doctrine DBAL, you can configure Jackalope:
162
162
session :
163
163
backend :
164
164
type : doctrinedbal
165
+ # connection: default
166
+
165
167
# requires DoctrineCacheBundle
166
168
# caches:
167
169
# meta: doctrine_cache.providers.phpcr_meta
@@ -193,6 +195,7 @@ Once you set up Doctrine DBAL, you can configure Jackalope:
193
195
logging =" true"
194
196
profiling =" true"
195
197
>
198
+ <!-- connection="default" - option on <backend> to change dbal connection -->
196
199
<!--
197
200
<caches
198
201
meta="doctrine_cache.providers.phpcr_meta"
@@ -211,6 +214,7 @@ Once you set up Doctrine DBAL, you can configure Jackalope:
211
214
'session' => array(
212
215
'backend' => array(
213
216
'type' => 'doctrinedbal',
217
+ //'connection': 'default',
214
218
'logging' => true,
215
219
'profiling' => true,
216
220
//'caches' => array(
@@ -234,7 +238,10 @@ Now make sure the database exists and initialize it:
234
238
235
239
.. tip ::
236
240
237
- Of course, you can also use a different connection instead of the default.
241
+ You can also use a different doctrine dbal connection instead of the
242
+ default. Specify the dbal connection name in the ``connection `` option of
243
+ the ``backend `` configuration.
244
+
238
245
It is recommended to use a separate connection to a separate database if
239
246
you also use Doctrine ORM or direct DBAL access to data, rather than
240
247
mixing this data with the tables generated by Jackalope Doctrine Dbal. If
You can’t perform that action at this time.
0 commit comments