3 ms·

Thanks for taking the time to respond. Actually, no. I want a single db to be the destination, receiving data from multiple tenant dbs. The tenant dbs do not

by rudasn 2y ago

Thanks for taking the time to respond. Actually, no. I want a single db to be the destination, receiving data from multiple tenant dbs. The tenant dbs do not have 'tenant' columns, but the destination would have one to differentiate between them. The use is being able to run reports against all tenant dbs with tools like metabase, or just plain sql, without having to access each tenant db individually. It's more involved that what I'm describing as db constraints and foreign keys / pk uniqueness would need to be worked around, but from first glance this tool seems like a good start towards that direction. What do you think?

shayonj 2y ago
Very interesting, I have wanted to solve this issue for a while and it actually overlaps with the "routing" feature for pg_flo that I am working on. Basically you can make map what data gets routed to what table and column in the destination DB, example [1]. Would be curious to get your thoughts/early impressions. [1] https://gist.github.com/shayonj/6105a6c7dde7a093ef55674fa966af4e https://gist.github.com/shayonj/6105a6c7dde7a093ef55674fa966...
- shayonj 2y ago
  I pushed out the v1. More deets at: https://github.com/shayonj/pg_flo/blob/main/pkg/routing/README.md https://github.com/shayonj/pg_flo/blob/main/pkg/routing/READ...