postgres-switch #113
No reviewers
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Activity
Doing
Activity
Proposal
Activity
QA
Activity
Validate
Runner
AT
Runner
CLI
Runner
HTTP
Runner
SSH
cleanup
devops
documentation
easypeasy
exchange
i18n
l8ter
legacy
meta
migration
optimization
privilege
refactor
smell
support
tooling
ux
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: urdt/ussd#113
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "postgres-switch"
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?
WIP: postgres-switchto postgres-switch@ -0,0 +1,34 @@
package initializers
I think convention is that file names in go be kept simple words. load.go will do
@ -0,0 +12,4 @@
pdbC map[string]chan db.Db
)
type ThreadPostgresDb struct {
i dont think you need the thread abstraction here, because the pg implementation used is already a managed connection pool. did you try it without?
@ -60,1 +71,4 @@
return nil, fmt.Errorf("failed to select the database")
}
if database == "postgres" {
postgres shouold be implemented for both userdatatstore and state store
@ -0,0 +1,74 @@
package storage
as we spoke about in meeting, i believe this file could be removed, and use the db from go-vise directly.
Confirmed. This has been done