How to use SQL Schema Explorer
Inspect real tables, columns, nullability, defaults and primary/unique/foreign key constraints from the PostgreSQL catalog in your selected local workspace.
- Choose a saved workspace or a sample dataset, then start PostgreSQL.
- Open Schema explorer and CSV data and select Inspect schema.
- Import a new CSV table if needed, inspect its columns, and export displayed query rows.
A practical starting point
CSV imports create a new table with text columns so leading zeroes and empty text remain intact. Add appropriate SQL types and constraints explicitly after reviewing your data.
SELECT table_name, column_name, data_type FROM information_schema.columns WHERE table_schema = 'public' ORDER BY table_name, ordinal_position;
Common mistakes
- CSV header and table names must be bounded ASCII SQL identifiers.
- An existing table is never overwritten by the CSV importer.
- CSV exports contain displayed rows only; the result display cap is not a limit on all database work.
Frequently asked questions
Are these conceptual schema examples?
The explorer reads the real running workspace catalog. Other SQL teaching pages remain labeled conceptual models.
Can a CSV cell inject SQL?
Cells are passed as SQL parameters. Identifiers are validated separately, and table creation/import runs in one transaction.
What happens to spreadsheet formulas?
CSV export protects risky cells with an apostrophe by default. Turn protection off only when you need original cell representations and understand the receiving application.