How can we improve Breeze.js?

338 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Thierry shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

11 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Ward Bell commented  ·   ·  Flag as inappropriate

    Sorry. Just have not got to it. There is a work around (not great) and we're working higher priorities. This is an open source project. We'd welcome your attempt at it and a PR.

  • cime commented  ·   ·  Flag as inappropriate

    More than 2 years... and still nothing new on this one?

  • Duncan Grist commented  ·   ·  Flag as inappropriate

    We've looked into how we could patch something on top of breeze to do this automatically, but because the foreign keys on dependent entities are NULLed before we get any event fired, it's complicated and messy to work out what entities should be detached/deleted when a parent entity is removed.

    So we would also very much like to see this behaviour as part of the core.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Steve, Jay, Ward.
    This is a pressing issue for us (We write our CTOR's with custom delete logic for each entity with childs)
    Cascade info. should be passed to the metadata so the client can support it.

    Regards,
    Ran Rosenmann - Yayasoft

  • Joe Warwick commented  ·   ·  Flag as inappropriate

    Cascade delete is exposed by the entity framework schema., so it is possible to provide this from metadata.
    I understand that breeze does not want to get into the referential integrity space a whole lot, but this particular item would greatly simplify client side model decorators.

  • Anonymous commented  ·   ·  Flag as inappropriate

    This is really needed when using DB cascaded deletes which is very common in one-to-many relationships...

Feedback and Knowledge Base