11–20 of 80 posts
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.
So happy to realize your stack includes Python, Postgres, Typescript and Svelte because I once flirted with such idea for a personal project. I'm inspired.
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.
Personally, I love types! (Can you tell that I'm on the front end team??) I used mypy extensively at my last job and liked it okay, but mypy is just not as nice as TypeScript. It's come a long way, but it can still be pretty cumbersome. TypeScript on the other hand is fantastic. I'm certainly never going back to JavaScript. But to get back to your original question: yes, for me using TypeScript has changed my tendency to use Python for other tasks. I just don't want to use Python as much. For backend work, I'd reach either for TypeScript, or for Rust. But keep in mind I'm just a front end dev! :)
[0]: https://mathesar.org/about.html [1]: https://github.com/centerofci/mathesar/discussions/913
So happy to realize your stack includes Python, Postgres, Typescript and Svelte because I once flirted with such idea for a personal project. I'm inspired.
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.
Have you ever tried [Pydantic](https://docs.pydantic.dev)!? It may be what you need for type safety / data validation.
Earlier quoted context omitted.
(Mathesar core team member here.) Thanks for the kind words! Our demo server actually spins up a unique database for each session, giving you the capability to make changes to the database and try Mathesar's features to the fullest extent. Your changes are only visible to you unless you send the link to someone else.
Could you elaborate that a bit? That sounds interesting too.
However, all databases are accessible to the demo user, so if you send a link to someone else, they will see your database (since the URL includes the database identifier).
You can see our code for it here: https://github.com/centerofci/mathesar/tree/develop/demo
[1] https://www.postgresql.org/docs/current/manage-ag-templatedb...
So happy to realize your stack includes Python, Postgres, Typescript and Svelte because I once flirted with such idea for a personal project. I'm inspired.
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.
I wouldn't try and write a decent-sized Python project without typing now.
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.
I haven't because I'm Python biased. ;) However, for Web I've found myself leaning to TypeScript for type-safety and DX reasons. Have you ever tried [Pydantic]( https://docs.pydantic.dev )!? It may be what you need for type safety / data validation.
icontract and pycontracts (Design-by-Contract programming) have runtime type and constraint checking; data validation. Preconditions, Command, Postconditions (assertions, assertions of invariance after command C_funcname executed) https://github.com/Parquery/icontract
pydantic_schemaorg: https://github.com/lexiq-legal/pydantic_schemaorg
> Pydantic_schemaorg contains all the models defined by schema.org. The pydantic classes are auto-generated from the schema.org model definitions that can be found on https://schema.org/version/latest/schemaorg-current-https.js... [ https://github.com/schemaorg/schemaorg/tree/main/data/releas... ]
This is super cool! I really dig the way airtable makes relational databases accessible to non-developers, but I've been looking for open source alternatives. Going to give this a spin this weekend :)
In Mathesar, we want the abstractions to be as thin as possible, while still giving non-technical users the capability to model and edit their data. You can point Mathesar and an existing Postgres database and, as long as all the foreign keys are in place, you should be able to use it a lot like Airtable. But when you set up a new relationship between tables, you'll find that it works very differently in Mathesar than in basically any other spreadsheet-database hybrid tool.
One-to-many relationships use a foreign key column in one table (instead of in two tables in Airtable). Many-to-many relationships use two FK columns in a join table (instead of by showing a column in each of the two related tables). All of the data is kept normalized. That normalization can make it hard to work with the data though! So we are developing a robust graphical query builder (called the "Data Explorer") which lets you to see data joined across multiple tables.
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.
Unlike SequelPro and TablePlus, we're a web application (although we do want to do a desktop version eventually). And Mathesar works even if you don't have an existing DB to connect to – you can set up a DB from scratch during installation.
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…
EDIT: demo server is back up.