Skip to content

#2697: forbid multiple @default breaks my workflow #2756

Description

@bvkimball

I don't think there is a reason to forbid a client-side default and a database default. I get that you can't necessarily determine based on implementation but i need and @PassThrough or an @db.default() or something.

Not all of the database creates go through my zenstack client. can i please have a workaround.

This blocks me from updating.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions