Hi all,
I am new to working with signals and triggers, what I am trying to
accomplish is:
1. When a new user registers, I have another model to deal with
subscriptions.
2. I want to create an instance for that subscription model with all the
default values based on the new user.
3.
Simple Answer: DON'T . Resort to signals only when there is No Alternatives
left.
Using Signals looks tempting but as project grows, it really becomes a Mess
to manage each of them. One simply becomes a confused and debugging becomes
a real Hell.
I suffered from this Problem. hence recommends t
Here is the relevant template from the link provided
>
>1.
>2.
>3.
>4.
>5. Employee Records
>6. {% load staticfiles %}
>7.
>8.
>9.
>10.
>11.
>12.
>13. Employee ID
>14. Employee Name
>15.
Disregard...Wrong thread.
On Sun, Mar 10, 2019 at 2:47 PM Kevin Jay wrote:
>
> Here is the relevant template from the link provided
>
>>
>>1.
>>2.
>>3.
>>4.
>>5. Employee Records
>>6. {% load staticfiles %}
>>7.
>>8.
>>9.
>>10.
>>
4 matches
Mail list logo
