-
Notifications
You must be signed in to change notification settings - Fork 32
WHERE_CLAUSE_REGEX bad escape problem #32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I hit a nearly identical issue with a similar stack trace after a routine dependencies upgrade -- just a different escape character. A common thread is that I also went from Django 4.1 => 4.2, so perhaps that is worth a closer look. One thing that jumps out at me in the Django 4.2 release notes is that Django 4.2 requires an update to Postgres 12+. Perhaps some of the database dependencies that are triggered as part of that major version update are at the root of this issue. https://docs.djangoproject.com/en/4.2/releases/4.2/#database-backend-api |
Getting similar issue with Django 3.2, GeoDjango, Postgres with postgis extension for only queries like this:
![]() Other ORM queries working fine. https://gis.stackexchange.com/questions/141533/geodjango-find-all-points-within-radius |
There is an unmerged PR that seems to fix this: #30 |
First of all: thanks so much for this module! I use it a shitload and it, basically, never lets me down. Appreciate it :)
I'm getting this little problemo with Django 4.2, Python 3.11, Psycopg 3.1.8:
Not exactly sure what's causing this, but thought it might be worth posting an issue about. Maybe data changed in some way between Django 4.1 and 4.2?
The text was updated successfully, but these errors were encountered: