Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you are using Git (or SVN or another source countrol tool) I would recommend to create two separate Symfony2 applications (each in its on repository). Also, every bundle gets its own repository and I would use Composer to set up the dependencies correctly and then install the bundles (LogicABundle, LogicBBundle, AppBundle) as vendors.</p> <p><strong>Update:</strong> Since the different bundles need different entities, one way is to specify the base entity in the bundle that does only need the base entity and extend the entity in the other bundle with additional relations (see <a href="http://docs.doctrine-project.org/en/2.0.x/reference/inheritance-mapping.html" rel="nofollow">Doctrine Inheritance Mapping</a>).</p> <p>For example, define <code>EntityA</code> in LogicABundle and define <code>EntityA2</code> in LogicBBundle where <code>EntityA2</code> extends <code>EntityA</code> and adds additional relations to the entity.</p> <p><strong>Update:</strong> Since you do not have provided additional information why you need to do this, I can only guess now, but one additional idea would be to simply use the same entities in both bundles. The logic in <code>LogicABundle</code> would simply ignore the additional relations. I think that is what most developers would do in your situation.</p> <p>Consider, for example, bundles that provide common functionality like FOSUserBundle. The bundle defines some models, but not every application that uses FOSUserBundle has to use every field of the entities (in a application I am currently developing I completely ignore the groups functionality of FOSUserBundle).</p> <p>Please provider further information if it is possible to use a common entity class and ignore these additional relations.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to setup Symfony2 Bundles independently with related Entities
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USFlorian Eckerstorfer
    1. USFlorian Eckerstorfer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1, **Composer** is the right way to proceed.
      singulars
      1. PO
      1. USFlorent
    2. COThe issue with this solution is that I need 2 versions of LogicABundle, the one with Entity relations to LogicBBundle and one without. I was just wondering wether there is a "clean" solution within Symfony2.
      singulars
      1. PO
      1. USm0c
    3. COWhen the entities are different in the both bundles you can't share them. You can either place them in the same bundle, but I would prefer separating them into different bundles. For example, CoreABundle contains the entities for LogicABundle and CoreBBundle the entities for LogicBBundle
      singulars
      1. PO
      1. USFlorian Eckerstorfer
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload