This page is archived.
- We decided to use limit/offset pagination instead of cursor pagination.
- We finalized on using TypeScript on the client.
- We finalized what we expect the Mathesar “Money” type to look like.
- We’re going to store timezones with local timezone information, not as UTC.
- We’re using
NUMERIC Postgres types to power our general “Number” type on the roadmap.
- We finalized implementation details for table creation from file imports.
- Mathesar should function as a GUI to existing DBs, although it does a lot more. There should only be one source of truth for database-related data.
- We’re using Svelte for the frontend.
- The frontend and backend code will live in the same repository.
- We’re storing web application related tables in a separate database.
- We’re using SQLAlchemy to interact with user-defined database objects rather than Django models.
- Reasoning: We don’t want to define user-defined database objects in code, we want the database to be the single source of truth and reflect what’s there.
- We’re using Django and Django REST Framework for the web application backend.
- Reasoning: We know it well and can build with it quickly.
- We’re using Python for the backend.
- Reasoning: We know it well and can build with it quickly.