Re: Possible design flaw: Modeler has no "none" option for "PK generation Strategy"

From: Mike Kienenberger (mkienen..mail.com)
Date: Thu Apr 13 2006 - 11:50:02 EDT

  • Next message: Andrus Adamchik: "Re: [OS-JIRA] Resolved: (CAY-503) Uniquing broken"

    Ok. It did get "smarter" once I switched my join table primary keys
    from "toMany" to "toOne".

    I still think there should be a way to manually specify both "none"
    and "auto pk table" primary key generation methods. I'll open a post
    1.2 jira issue.

    On 4/13/06, Mike Kienenberger <mkienen..mail.com> wrote:
    > There's also no way to force it to use a table for pk generation.
    > The choices are:
    >
    > default -- for Oracle, make up a sequence
    > database-generated - autoinc columns
    > custom -- specify a sequence
    >
    > On 4/13/06, Mike Kienenberger <mkienen..mail.com> wrote:
    > > As I rebuild my schemas on Oracle today, I notice that there's no way
    > > to specify not to create a "PK generation Strategy" for a join table
    > > with only dependent primary keys.
    > >
    > > I was hoping that "default" would work, but I was expecting too much :)
    > >
    >

    This archive was generated by hypermail 2.0.0 : Thu Apr 13 2006 - 11:50:34 EDT