41–50 of 80 posts
Love the reference to GalaxyQuest. (Mathesar was the Thermian leader.)
We also intend to release our Svelte component-library as a separate package and considering if we should establish a GalaxyQuest theme when naming it, perhaps Laliari.
Here's the discussion: https://github.com/centerofci/mathesar/discussions/833
Earlier quoted context omitted.
If I may ask, have you found using a Typed language such as Typescript has changed your tendency to use Python for other tasks, given that it isn't typed? [0] [0] - I understand that types can be added on top, but I never found the integration to work that well with mypy when I last tried it many years ago.
Typescript has made me stop loving Python. I wish Python typing was powerful enough to be as complete as TS.
Not to distract from this project — it's very cool! — but I'd love to know if there's something similar in principle to this, but that's focused less on collaborative querying , and more on collaborative database administration . Specifically, I've been in the market for a while now for a webapp you can run on a server, that presents a UX for submitting, watching the progress, and managing, long-running schema change…
It's also not free and breaks in all kinds of fun ways.
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?
Schema migrations should go via CI/CD and data changes via your app.
Otherwise it’s gets messy indeed.
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.
Feature request: historical tracking. E.g. on update, expire the old record with who & when.
I won't repeat supportive comments except to say well done. Feature request: historical tracking. E.g. on update, expire the old record with who & when.
We have had discussions regarding auditing in Mathesar[1], though it's not explicitly documented in the roadmap yet. We do have plans to implement Undo & Redo support for data editing operations in our roadmap[2] which would depend on the auditing implementation.
[1] https://github.com/centerofci/mathesar/discussions/113#discu... [2] https://mathesar.org/roadmap.html
This looks great and congratulations on the alpha launch! Reminds me of another open source project in this space, NocoDB. Are you guys familiar with that project? If so, what are the main differences between them and what you are offering?
We've documented the differences between Mathesar and other similar products including NocoDB on the FAQ section[1] in our website.
[1] https://mathesar.org/faq.html#how-is-mathesar-different-from...
The schema migrations are a delight. And I appreciate the shoutout to Dabble! Thanks for working on this + congrats on the release. An optimized hosted version with permalinks to Explorer views would open access to even more users.
A hosted version is definitely on our plans for Mathesar, and being able to share tables and explorations publicly via a permalink is part of our roadmap[1][2].
[1] https://mathesar.org/roadmap.html [2] https://github.com/centerofci/mathesar/discussions/2266