Live data from Hacker News

Show HN: Mathesar – open-source collaborative UI for Postgres databases

github.com

21–30 of 80 posts

Re: Show HN: Mathesar – open-source collaborative UI for Postgres databases

#25
post #9

Nice work! It looks like Sequel Pro for Postgres. This might be the first free, user-friendly interface for Postgres out there. Closest would be TablePlus but it’s paid.

https://github.com/beekeeper-studio/beekeeper-studio is pretty decent.

Re: Show HN: Mathesar – open-source collaborative UI for Postgres databases

#26
I'm sorry if this question is stupid, I'm still learning a little about technology. The little bit of knowledge I have tells me that my product team shouldn't directly access the same production database as my application. The idea for this product would be to create a copy of my production base and give access to it through this tool? Wouldn't the cost of this replica be too expensive?

Re: Show HN: Mathesar – open-source collaborative UI for Postgres databases

#27
post #26

I'm sorry if this question is stupid, I'm still learning a little about technology. The little bit of knowledge I have tells me that my product team shouldn't directly access the same production database as my application. The idea for this product would be to create a copy of my production base and give access to it through this tool? Wouldn't the cost of this replica be too expensive?

In my experience in tech, most teams directly access and manipulate production frequently. Bigger companies usually have restrictions on this but in the start up world not so much.

Re: Show HN: Mathesar – open-source collaborative UI for Postgres databases

#29
post #14

Earlier quoted context omitted.

Could you elaborate that a bit? That sounds interesting too.

Yes! We have set up a Postgres template database[1] with our demo data sets. When a user logs in, we create a new database based on the template database and associate the database with the session key set up for that login. So every session is associated with a different database and we have some Django middleware that routes you to the URL associated with your session's database. If you log out and log back in (thu…

How on earth are you handling HN front page traffic if you spin up a template copy per session? That is impressive.

Re: Show HN: Mathesar – open-source collaborative UI for Postgres databases

#30
post #29
post #14

Earlier quoted context omitted.

Yes! We have set up a Postgres template database[1] with our demo data sets. When a user logs in, we create a new database based on the template database and associate the database with the session key set up for that login. So every session is associated with a different database and we have some Django middleware that routes you to the URL associated with your session's database. If you log out and log back in (thu…

How on earth are you handling HN front page traffic if you spin up a template copy per session? That is impressive.

You’d be (pleasantly) surprised how easy it is to copy a postgres database. It literally copies the data files for the database to a new directory so the operation is relatively quick if the total volume of data is not large.

What’s more challenging is handling many concurrent connections as a different database would mandate a separate connection and you can’t perform any meaningful connection pooling.

Post reply on HN