Re: Kindly Help
On 27/06/2022 21.14, Habib ur rehman wrote: > raise MigrationSchemaMissing( > django.db.migrations.exceptions.MigrationSchemaMissing: Unable to create the > django_migrations table ((1064, "You have an error > in your SQL syntax; check the manual that corresponds to your MySQL server > version for the right syntax to use near '(6) NOT NULL)' at line 1")) > This should provide the help you need: http://www.catb.org/~esr/faqs/smart-questions.html Kind regards, Kasper Laudrup -- 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 django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/72682CC5-DE9C-41CE-AEA0-7FC0BDDF82F8%40stacktrace.dk.
Re: Could not parse the remainder: '='dashboard'' from 'section='dashboard''
The problem is the lack of space between section and the ==, as well as a missing = My answer here can be of help: https://stackoverflow.com/a/7260/7109869 On Friday, November 22, 2019 at 7:04:41 PM UTC allaberdi...@gmail.com wrote: > [image: Capture.JPG] > > > > -- 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 django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/f0ec339a-e2d3-417d-83fe-534356e66f91n%40googlegroups.com.
Re: Kindly Help
On 27/06/2022 21.14, Habib ur rehman wrote: > raise MigrationSchemaMissing( > django.db.migrations.exceptions.MigrationSchemaMissing: Unable to create the > django_migrations table ((1064, "You have an error > in your SQL syntax; check the manual that corresponds to your MySQL server > version for the right syntax to use near '(6) NOT NULL)' at line 1")) > This should provide the help you need: http://www.catb.org/~esr/faqs/smart-questions.html Kind regards, Kasper Laudrup -- 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 django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/0E153B5A-77A5-4B76-9FEE-5CE903F63986%40stacktrace.dk. OpenPGP_0xE5D9CAC64AAA55EB.asc Description: application/pgp-keys
Re: Kindly Help
On 27/06/2022 21.14, Habib ur rehman wrote: raise MigrationSchemaMissing( django.db.migrations.exceptions.MigrationSchemaMissing: Unable to create the django_migrations table ((1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(6) NOT NULL)' at line 1")) This should provide the help you need: http://www.catb.org/~esr/faqs/smart-questions.html Kind regards, Kasper Laudrup -- 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 django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9d933d09-5710-3be1-3a75-4f36d4b17530%40stacktrace.dk. OpenPGP_0xE5D9CAC64AAA55EB.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Kindly Help
raise MigrationSchemaMissing( django.db.migrations.exceptions.MigrationSchemaMissing: Unable to create the django_migrations table ((1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(6) NOT NULL)' at line 1")) -- 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 django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/3ac3f996-801a-4dfc-9447-27341a717e4cn%40googlegroups.com.
Re: hr and employee login api in django authendication
On 27/06/2022 11.03, Ganush K wrote: hr and employee login api in django authendication ..plz help ..hr view 1.total employee ,salry mangement then employee view only our account..any code or refer any things share me.. ganushgm2...@gmail.com If you want someone to help you at least spent some time writing a question/request people have a chance of understanding. Right now you just sound like a jerk and I doubt anyone will even consider doing anything to help you and that's not only because nobody has any idea what you are talking about. Kind regards, Kasper Laudrup -- 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 django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/c845995d-ec5a-e367-3828-731f77e7f089%40stacktrace.dk. OpenPGP_0xE5D9CAC64AAA55EB.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
hr and employee login api in django authendication
hr and employee login api in django authendication ..plz help ..hr view 1.total employee ,salry mangement then employee view only our account..any code or refer any things share me.. ganushgm2...@gmail.com -- 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 django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/f5a49691-37b3-4a20-a50a-857c4cbb8bd0n%40googlegroups.com.
Does Django care about max_query_params? [feature request]
Hi, all! Gotta problem with the number of query params. We're using a backend, which connects to a cloud database, and at some point we suddenly started getting such an error: *Number of parameters in query exceeds the maximum allowed limit of 950* Appearing on this step: *django/django/contrib/auth/management/__init__.py", line 83, in create_permissionsPermission.objects.using(using).bulk_create(perms)* 950 query params is the max number for our backend, and we set the *DatabaseFeatures.max_query_params *to 900. Still, it looks like Django doesn't care. Because of this all of our tests stopped working, bringing a lot of inconveniences during development. Seems to me that it should be fixed on Django side, centralized, 'cause it's unlikely we're the only who met and will meet the problem in future. -- 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 django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9a1a3b9c-62a1-496d-ab7e-b12cb5560994n%40googlegroups.com.
How to ignoring columns on model save
I have a model that is backed by a database table that contains a read-only column that is maintained by the database using Postgresql's Generated Columns (i.e. using GENERATED ALWAYS AS) - see https://www.postgresql.org/docs/current/ddl-generated-columns.html. When Django saves the model, it tries to set the field, which throws `django.db.utils.ProgrammingError: cannot insert into column "_search". DETAIL: Column "_search" is a generated column. Is there any way to tell Django not to attempt to insert that field? >From what I can tell `editable=False` doesn't prevent Django from trying to save it - which makes sense for fields that aren't editable by users but are calculated by the model class, e.g. in `save()`. I know I could set `something like `instance.save(update_fields=[field for field in instance._meta.fields if field.name != "_search")` but it would need to be set on every save for that model throughout the application, which seems like a lot of technical debt and likely to trip up other developers as they maintain the application. Is there anything that I can set on the field instance in the model to tell Django that it is maintained by the database? If not, please can anyone suggest a way to add code to the model to make it ignore the field when saving? Thanks Roger -- 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 django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5b17444e-48ad-4bb6-b9b0-43a186ed3525n%40googlegroups.com.
Re: How to generate a table in pdf?
https://xhtml2pdf.readthedocs.io/en/latest/usage.html is what you need. On Friday, 24 June 2022 at 16:08:10 UTC+2 kvnk...@gmail.com wrote: > > > > > *Hi family, I created a salary calculation application.As I already > display the list of employees, I now have to download it using a function > in the VIEW folder.Please I urgently need helpThanks ...* > -- 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 django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/b7b33563-6fae-445c-8343-1dad5e976a1en%40googlegroups.com.
