Watch, Follow, &
Connect with Us

Please visit our new home
community.embarcadero.com.


Welcome, Guest
Guest Settings
Help

Thread: Cascading Deletes and Updates in FireDAC with C++ Builder


This question is not answered. Helpful answers available: 2. Correct answers available: 1.


Permlink Replies: 2 - Last Post: Mar 22, 2018 9:34 PM Last Post By: Matthew Grayson
Ahmed Sayed

Posts: 173
Registered: 8/9/07
Cascading Deletes and Updates in FireDAC with C++ Builder  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 15, 2018 6:51 PM
Hello,

I am facing a problem where i can't cascade deletes
and updates in FireDAC as it were the case with
Datasnap where you get poCascadeDeletes,
poCascadeUpdates and you are done.

Now, I followed the centralized cached updates help and
it works but it will force me to write ApplyUpdates every time
i make a change to the database.

Now, What i want to achieve is this.
- I don't want to link tables on the database level
- I don't want to use SchemaAdapters.
- I don't want to use cached updates.
- I want the link tables on the application level and
cascade deletes correctly.

Any help will be truly appreciated. Thanks in advance
--
The limits of my language mean the limits of my world
Ahmed Sayed

Posts: 173
Registered: 8/9/07
Re: Cascading Deletes and Updates in FireDAC with C++ Builder  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 21, 2018 8:04 AM   in response to: Ahmed Sayed in response to: Ahmed Sayed
Can someone please help me with this I stuck...?

--
The limits of my language mean the limits of my world
Matthew Grayson

Posts: 8
Registered: 12/26/02
Re: Cascading Deletes and Updates in FireDAC with C++ Builder  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 22, 2018 9:34 PM   in response to: Ahmed Sayed in response to: Ahmed Sayed
Hmmm - I don't have the experience with this paradigm, but I did take a look on Stackexchange. I think from what I read there that you will have success with your question.

Now, I followed the centralized cached updates help and
it works but it will force me to write ApplyUpdates every time
i make a change to the database.

My first thought here is why not use ApplyUpdates? Are the changes you make to massive or is it time consuming or something?

Now, What i want to achieve is this.
- I don't want to link tables on the database level
- I don't want to use SchemaAdapters.
- I don't want to use cached updates.
- I want the link tables on the application level and
cascade deletes correctly.

Any help will be truly appreciated. Thanks in advance

That's a lot of I Don'ts - is it possible that what you are attempting may not yield to what you dos and don'ts are allowing for?

I would really go look at stackexchange and see if someone doesn't have a good suggestion for you.

Sorry I could be more of a help.

Atomkey.
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02