You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by "Tore Halset (JIRA)" <de...@cayenne.apache.org> on 2007/12/18 10:11:44 UTC

[JIRA] Commented: (CAY-937) Database Schema Migration does not create FK constraints.

    [ https://issues.apache.org/cayenne/browse/CAY-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12639 ] 

Tore Halset commented on CAY-937:
---------------------------------

We already have code for adding a FK, so that one should not be too hard. Dropping a FK seem to be a bit more difficult. Both PostgreSQL and Derby support "alter table ... drop constraint fkname", but it can be hard to find the correct foreign key name.



> Database Schema Migration does not create FK constraints.
> ---------------------------------------------------------
>
>                 Key: CAY-937
>                 URL: https://issues.apache.org/cayenne/browse/CAY-937
>             Project: Cayenne
>          Issue Type: Improvement
>          Components: Cayenne Core Library
>    Affects Versions: 3.0
>            Reporter: Kevin Menard
>            Assignee: Tore Halset
>            Priority: Minor
>             Fix For: 3.0
>
>
> It'd be nifty if the database schema migration tool could detect if a FK relationship needs to be set up.  The DB generation function can set up FK relationships as is, so hopefully it's not too great a stretch to make it work with the migration tool as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.