StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7534238
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-09-23T20:06:06.383
FavoriteCount
0
LastActivityDate
2011-09-23T20:06:06.383
LastEditDate
LastEditorUserId
0
OwnerUserId
393172
ParentId
7104937
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
What you're wanting is not "technically" supported as a design feature in Doctrine. So if you're wanting to do this as you would with traditional PostgreSQL: <pre><code>SELECT table1.field1, table1.field2, table2.field2, FROM table1 INNER JOIN dblink('dbname=db2 port=5432 host=domainname2 user=someuser password=somepwd', 'SELECT field1, field2, FROM other_table') AS table2(field1 int, field2 char(25)) ON table1.field3 = table2.field1; </code></pre> You would replace the single connection that's default in your config.php file with two connections. <pre><code><?php Doctrine_Manager::connection('mysql://root@server1/doctrine_db1', 'db1'); Doctrine_Manager::connection('mysql://root@server2/doctrine_db2', 'db2'); </code></pre> Then you'd modify your schema with something like this: <pre><code>--- Table1: tableName: db1.table1 connection: db1 columns: filed1: integer field2: string(255) field3: integer relations: Table2: foreignType: one onDelete: CASCADE Table2: tableName: db2.table2 connection: db2 columns: field1: integer field2: string(25) </code></pre> Then you'd build the database after adding data like normal. Then just do your regular modeling, making sure to specify the table with the field you want like you would with any regular query. <a href="http://www.doctrine-project.org/blog/cross-database-joins" rel="nofollow">Doctrine Cross Database Joins</a> are discussed in detail on the Doctrine blog. So you might check it out.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJoin across different databases on different servers in Doctrine and PostgreSQL
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USrexibit
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThe correct link to the Doctrine blog entry mentioned above is : http://www.doctrine-project.org/blog/cross-database-joins.html I tried editing the post to correct the link but it fell short of the minimum '6' characters required for the edit.
 singulars
 PostPostId
 PO
 UserUserId
 USs1d

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.