Changing SEARCH_PATH in Postgres does not work intermittently #379
Labels
No Label
backport/done
backport/v1
blocked
db
oracle
db
sqlserver
duplicate
feature
cache
frontport/done
frontport/main
invalid
kind
breaking
kind
bug
kind
build
kind
dependencies
kind
docs
kind
driver
kind
enhancement
kind
feature
kind
performance
kind
proposal
kind
question
kind
refactor
kind
testing
need
feedback
need
test
proposal:accepted
RaspBerry Pi
regression
skip-changelog
upstream
wip
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: xorm/xorm#379
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
We are using xorm with great result with Postgres. But we are seeing an issue that happens intermittently. We use non-public schema and run the following command before accessing tables:
store.Engine.Exec("SET SEARCH_PATH TO \"myschema\"")
Sometimes, this does not seem to have any effect and queries keep running against the public schema. This will happen on one computer with same code but not on other computers. Then it will sort of fix on its own. Is there something we are doing wrong? Is xorm reusing connections is some way to cause this?
Thanks.
We found out that if we roll back to v0.5.0 for xorm and core package then public schema error goes away. @lunny, can you please revert the schema connection param change and hopefully, we can start using master again.
@codefx9, I have remove all the schema code and you can test your code to confirm the issue is fixed. And you can reopen it if your issue is still not resolved.