<i id='F1Rq2'><tr id='F1Rq2'><dt id='F1Rq2'><q id='F1Rq2'><span id='F1Rq2'><b id='F1Rq2'><form id='F1Rq2'><ins id='F1Rq2'></ins><ul id='F1Rq2'></ul><sub id='F1Rq2'></sub></form><legend id='F1Rq2'></legend><bdo id='F1Rq2'><pre id='F1Rq2'><center id='F1Rq2'></center></pre></bdo></b><th id='F1Rq2'></th></span></q></dt></tr></i><div id='F1Rq2'><tfoot id='F1Rq2'></tfoot><dl id='F1Rq2'><fieldset id='F1Rq2'></fieldset></dl></div>
    <legend id='F1Rq2'><style id='F1Rq2'><dir id='F1Rq2'><q id='F1Rq2'></q></dir></style></legend>

    <small id='F1Rq2'></small><noframes id='F1Rq2'>

  1. <tfoot id='F1Rq2'></tfoot>

      • <bdo id='F1Rq2'></bdo><ul id='F1Rq2'></ul>

      Doctrine 1 和 Symfony 1 的多个主键?

      Multiple primary keys with Doctrine 1 and Symfony 1?(Doctrine 1 和 Symfony 1 的多个主键?)

              <tbody id='kcINe'></tbody>

            • <bdo id='kcINe'></bdo><ul id='kcINe'></ul>

              <i id='kcINe'><tr id='kcINe'><dt id='kcINe'><q id='kcINe'><span id='kcINe'><b id='kcINe'><form id='kcINe'><ins id='kcINe'></ins><ul id='kcINe'></ul><sub id='kcINe'></sub></form><legend id='kcINe'></legend><bdo id='kcINe'><pre id='kcINe'><center id='kcINe'></center></pre></bdo></b><th id='kcINe'></th></span></q></dt></tr></i><div id='kcINe'><tfoot id='kcINe'></tfoot><dl id='kcINe'><fieldset id='kcINe'></fieldset></dl></div>

                <tfoot id='kcINe'></tfoot>

                <small id='kcINe'></small><noframes id='kcINe'>

              1. <legend id='kcINe'><style id='kcINe'><dir id='kcINe'><q id='kcINe'></q></dir></style></legend>
              2. 本文介绍了Doctrine 1 和 Symfony 1 的多个主键?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着跟版网的小编来一起学习吧!

                问题描述

                我已经知道在 Symfony 1 和 Doctrine 1 中不能使用多个主键,但是你们知道有什么好的解决方法吗?

                I already know that's not possible to work with multiple primary keys in Symfony 1 and Doctrine 1, but do you guys know any good workarounds?

                推荐答案

                一种常见的解决方法是在多对多解析器表中添加一个 auto_increment 键,而不是定义关系,只需建立标准的外键关系即可桌子.只要您在两列上都有索引,性能就可以了.

                A common workaround is to add an auto_increment key to the many-to-many resolver table, and rather than have defining relationships, just make standard foreign key relationships to the tables. As long as you have an index on the two columns performance will be fine.

                这篇关于Doctrine 1 和 Symfony 1 的多个主键?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

                本站部分内容来源互联网,如果有图片或者内容侵犯了您的权益,请联系我们,我们会在确认后第一时间进行删除!

                相关文档推荐

                When should use doctrine ORM and when zend-db-table?(什么时候应该使用学说 ORM,什么时候应该使用 zend-db-table?)
                Doctrine - self-referencing entity - disable fetching of children(Doctrine - 自引用实体 - 禁用获取子项)
                Doctrine 2, query inside entities(原则 2,实体内部查询)
                Complex WHERE clauses using the PHP Doctrine ORM(使用 PHP Doctrine ORM 的复杂 WHERE 子句)
                Doctrine - OneToMany relation, all result row doesn#39;t fetch in object(Doctrine - OneToMany 关系,所有结果行不获取对象)
                Doctrine and unrefreshed relationships(教义和未更新的关系)

                  <tfoot id='gegQA'></tfoot>
                    <bdo id='gegQA'></bdo><ul id='gegQA'></ul>
                    <legend id='gegQA'><style id='gegQA'><dir id='gegQA'><q id='gegQA'></q></dir></style></legend>

                    1. <small id='gegQA'></small><noframes id='gegQA'>

                        <tbody id='gegQA'></tbody>

                        • <i id='gegQA'><tr id='gegQA'><dt id='gegQA'><q id='gegQA'><span id='gegQA'><b id='gegQA'><form id='gegQA'><ins id='gegQA'></ins><ul id='gegQA'></ul><sub id='gegQA'></sub></form><legend id='gegQA'></legend><bdo id='gegQA'><pre id='gegQA'><center id='gegQA'></center></pre></bdo></b><th id='gegQA'></th></span></q></dt></tr></i><div id='gegQA'><tfoot id='gegQA'></tfoot><dl id='gegQA'><fieldset id='gegQA'></fieldset></dl></div>