You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on an application that uses two different databases. The primary database is the RW database for my application while the secondary database is a static data (read-only) database produced by a third-party as an ease of use feature. Currently I use SQLC to generate all my golang types and queries for both databases, however, I'm starting to run into challenges of dynamic data in the RW database needing to be joined with static data of the secondary database.
I'm wondering if this is a scenario others have run into and if there would be any interest in extended SQLC to support attaching secondary databases?
(Not looking for others to implement, just seeing if there's enough interest to justify implementing it myself)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm currently working on an application that uses two different databases. The primary database is the RW database for my application while the secondary database is a static data (read-only) database produced by a third-party as an ease of use feature. Currently I use SQLC to generate all my golang types and queries for both databases, however, I'm starting to run into challenges of dynamic data in the RW database needing to be joined with static data of the secondary database.
I'm wondering if this is a scenario others have run into and if there would be any interest in extended SQLC to support attaching secondary databases?
(Not looking for others to implement, just seeing if there's enough interest to justify implementing it myself)
Beta Was this translation helpful? Give feedback.
All reactions