I hope you can understand the security implications of this and are knowledgeable on the places where you need to lock down access. On Wednesday, May 24, 2023 at 6:47:14 AM UTC-4 Helly Modi wrote:
> we have to create this project where user can enter all details of table > from frontend and table is created in backend so this idea was given where > these and have to work on this idea only.see image for better understanding. > > On Wed, May 24, 2023 at 4:10 PM Anh Nguyen <[email protected]> wrote: > >> So what is your problems and why do we need a dynamic table? >> >> On Wed, 24 May 2023 at 14:34 Helly Modi <[email protected]> wrote: >> >>> worked on this option only .even tried dynamic django models but didn't >>> work because of sustainable.if someone have the options or way to handle >>> then please give >>> >>> >>> On Wednesday, May 24, 2023 at 11:06:23 AM UTC+5:30 Anh Nguyen wrote: >>> >>>> Even your migrate works fine but you have to reload your runtime to >>>> apply new codebase to de-encode data. So go back and find another solution. >>>> >>>> On Wed, 24 May 2023 at 12:22 Helly Modi <[email protected]> wrote: >>>> >>>>> I have to create dynamic table at runtime where user enters the >>>>> details of table name,table column,table fields,constraints.take this >>>>> input >>>>> in backend and create table dynamically without creating schemas of >>>>> tables >>>>> as tables are created at runtime .first approach is that we will create >>>>> one >>>>> table where all the fields are mentioned where primary key,secondary >>>>> key,unique,not niull and all the constraints are mentioned in horizontal >>>>> column.now we have to create table 2 where user will select whild field >>>>> id >>>>> he want to select .suppose if user wants to create primary key then it >>>>> will >>>>> select field 1 in second table so it is refered from main table.and then >>>>> table is created do you know how this works in django from backend side >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Django users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/django-users/24b3cec9-f614-4592-a1de-e69f2a71bc3fn%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/django-users/24b3cec9-f614-4592-a1de-e69f2a71bc3fn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-users/104d78f3-3aa0-4962-a640-d4a59eca717fn%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/django-users/104d78f3-3aa0-4962-a640-d4a59eca717fn%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/CAKaoNbT0DsxHt_N6L%2B%2Bn-YV-KrGY%2BN8onNAymkOq2BxAVGO99Q%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/django-users/CAKaoNbT0DsxHt_N6L%2B%2Bn-YV-KrGY%2BN8onNAymkOq2BxAVGO99Q%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a0f96f17-8881-4bb4-9540-fe0d38594d63n%40googlegroups.com.
