Migrate away from bob as a SQL generation layer #32
Loading…
Add table
Add a link
Reference in a new issue
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?
Previously I investigated using Bob. I ran into major limitations related to working with PostGIS data. We've been moving toward go-jet, but right now we are using both. I'm suspicious that #3 is at least partially caused or obscured by the double database pooling system that comes with using bob.
Let's finish getting off of it.
We currently have bob-related imports in:
ee82100a0adeals withplatform/arcgis.goa4b2031461deals withplatform/compliance.goFixed in
782a49f220