Skip to content

OneToOne Constraints #7819

Open
Open
@parljohn

Description

@parljohn

I have a database that I can't change or control because it is used in a windows application. I have to extend the database by creating extended onetoone tables but I don't pre-populate the tables with rows. This causes all my OnetoOne relationships to break because of the non-existing records. I get the need for the constraints, but why not a way out? Why now allow for a record to be auto-generated like a cascade "auto-generate" or something if it doesn't exist yet instead of just throwing exceptions?

Secondarily, when I add a new object to act in the place of the onetoone, it tries to update a non-updatable auto generated ID on the table i'm joining it to and that throws an exception as well.

It's pretty frustrating trying to find a way around this and still use the convenience of the relationship. Any input would help, thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions