Re: How can I work around the Django 3.2.10 cve release

Hi mike and jason kindly help me to my query also i have shared my query in group its emergency *my humble request :-* please help me here i do have some columns called *sub_task_name* tht should every day update same perivous task_name but* sub_task_value* shld not update it shld give opt

please help in updation

here i have secenario like there when user moved for a done is sub_task_name shld be same perivos updated task but new updation option shld get sub_task_value tht option shld get user has same as in task_name shld be previous updated task but for user shld get new value entring option for

please help in updates coulmns

*my humble request :-* please help me here i do have some columns called *sub_task_name* tht should every day update same perivous task_name but* sub_task_value* shld not update it shld give option to user to enter new value same criteria for* task_name *shld be same perivous entered but

Using database tables without creating models for each table

mandatory? Is there any alternative? Thanks, Lavanya --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubsc