That fixed it!
On Thursday, April 21, 2016 at 3:30:39 PM UTC-4, Anthony wrote:
>
> Try with a fresh table and see if cascade works.
>
> On Thursday, April 21, 2016 at 3:27:25 PM UTC-4, Mark Billion wrote:
>>
>> It was added later.
>>
>> On Thursday, April 21, 2016 at 3:23:19 PM UTC-4, Anthony wrot
Try with a fresh table and see if cascade works.
On Thursday, April 21, 2016 at 3:27:25 PM UTC-4, Mark Billion wrote:
>
> It was added later.
>
> On Thursday, April 21, 2016 at 3:23:19 PM UTC-4, Anthony wrote:
>>
>> Was Income_Src a reference field when you first created the table, or did
>> you
It was added later.
On Thursday, April 21, 2016 at 3:23:19 PM UTC-4, Anthony wrote:
>
> Was Income_Src a reference field when you first created the table, or did
> you make that change later?
>
> On Thursday, April 21, 2016 at 2:16:10 PM UTC-4, Mark Billion wrote:
>>
>> No, I mean the first one.
Was Income_Src a reference field when you first created the table, or did
you make that change later?
On Thursday, April 21, 2016 at 2:16:10 PM UTC-4, Mark Billion wrote:
>
> No, I mean the first one. I delete an income entry and the associated
> deduction entries still stick around.
>
> Bt
No, I mean the first one. I delete an income entry and the associated
deduction entries still stick around.
On Thursday, April 21, 2016 at 2:11:34 PM UTC-4, Leonel Câmara wrote:
>
> Do you mean you delete something in table "income" and nothing is deleted
> in "deductions"?
>
> Or do you me
Do you mean you delete something in table "income" and nothing is deleted
in "deductions"?
Or do you mean you delete something from the set DEBTOR_TOGGLE_NO_BOTH and
no row is deleted in table "income"?
The second one is obviously to be expected since cascading is a database
operation and the
6 matches
Mail list logo
