Propel 中不完整的关键参考有用吗?
我正在使用 Propel 开发一个系统,用户可以在其中开发自己的模式,因此我正在研究一些“边缘情况”。我遇到了一个我认为 Propel 应该禁止的模式,但它似乎确实可以构建。任何人都可以建议一个用例吗?
<?xml version="1.0" encoding="UTF-8"?>
<database name="test" defaultIdMethod="native">
<table name="test_event">
<column name="id" type="integer" required="true" primaryKey="true" autoIncrement="true" />
<column name="name" type="varchar" size="50" required="true" />
<column name="description" type="varchar" size="250" />
<column name="location" type="varchar" size="250" />
<column name="nearest_city" type="varchar" size="100" />
<column name="organiser_id" type="integer" required="true" />
<!-- This FK is incomplete -->
<foreign-key foreignTable="test_organiser">
<reference local="organiser_id" foreign="id" />
</foreign-key>
</table>
<table name="test_organiser">
<!-- Has composite PK -->
<column name="id" type="integer" required="true" primaryKey="true" autoIncrement="true" />
<column name="secondary" type="integer" required="true" primaryKey="true" />
<column name="name" type="varchar" size="50" required="true" />
<column name="email" type="varchar" size="100" />
</table>
</database>
正如您所看到的,事件表对组织者表有不完整的外部引用。我本以为 Propel 会检测到这一点并在构建时将其踢出 - 但显然没有!我不明白为什么这会有用 - BaseTestEvent
中的 setTestOrganiser
和 getTestOrganiser
方法仅引用复合 PK 的一部分(因为当然,活动方只知道organiser_id部分)。
推进 1.6.1、PHP 5.2.17。
I am using Propel to develop a system in which users can develop their own schemas, so am looking at some "edge cases". I have come across a schema that I think Propel should disallow, but it does seem to build. Can anyone suggest a use case for this?
<?xml version="1.0" encoding="UTF-8"?>
<database name="test" defaultIdMethod="native">
<table name="test_event">
<column name="id" type="integer" required="true" primaryKey="true" autoIncrement="true" />
<column name="name" type="varchar" size="50" required="true" />
<column name="description" type="varchar" size="250" />
<column name="location" type="varchar" size="250" />
<column name="nearest_city" type="varchar" size="100" />
<column name="organiser_id" type="integer" required="true" />
<!-- This FK is incomplete -->
<foreign-key foreignTable="test_organiser">
<reference local="organiser_id" foreign="id" />
</foreign-key>
</table>
<table name="test_organiser">
<!-- Has composite PK -->
<column name="id" type="integer" required="true" primaryKey="true" autoIncrement="true" />
<column name="secondary" type="integer" required="true" primaryKey="true" />
<column name="name" type="varchar" size="50" required="true" />
<column name="email" type="varchar" size="100" />
</table>
</database>
As you can see, the event table has an incomplete foreign reference to the organiser table. I'd have thought Propel would have detected that and kicked it out at build time - but apparently not! I can't see why this would be useful - the setTestOrganiser
and getTestOrganiser
methods in BaseTestEvent
only refer to one part of the composite PK (because, of course, the event side is only aware of the organiser_id part).
Propel 1.6.1, PHP 5.2.17.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
不,它们没有用。 Propel 目前还没有针对此用例的检查。我已经为它创建了一个问题,这样当我们已经实施了。
No they're not useful. Propel does just not have a check for this use case at the moment. I've created a issue for it so you won't stumble over it again when we've implemented it.