square_database_structure
📌 versioning: see CHANGELOG.md.
about
python module to define postgresql database schemas using sqlalchemy.
goals
- clear database → schema → table hierarchy
- reusable (template) across multiple projects
- single source of truth for schema and data
installation
pip install square_database_structure
usage
this module organizes database schemas in a standardized folder structure where each top-level folder represents a
database, and subfolders within it represent schemas. all mandatory components, such as __init__.py and tables.py,
data.py, stored_procedures_and_functions need to follow this structure.
folder structure
square_database_structure/
├───main.py # global definition file (mandatory)
├───create_database.py # global database creation file (mandatory)
└───database1/ # each folder corresponds to a separate database
├───__init__.py # contains the global name for the database (mandatory)
└───schema1/ # each subfolder corresponds to a schema within the database
├───__init__.py # contains the global name for the schema (mandatory)
├───data.py # contains the data for insertion for the schema (mandatory)
├───enums.py # defines enums to be used in the schema (optional)
├───tables.py # defines tables of the schema (mandatory)
└───stored_procedures_and_functions/ # contains stored procedures and functions for the schema (mandatory)
├───__init__.py # contains logic to discover sql files (mandatory)
└───function1.sql # function or stored procedure sql file (optional)
- top-level folders: represent individual databases (e.g., database1).
- subfolders: represent schemas within each database (e.g., public, schema1).
- mandatory files:
__init__.py(both at the database and schema level).- tables.py within each schema.
- data.py within each schema.
- stored_procedures_and_functions package within each schema.
defining database and schema names in __init__.py
each database and schema folder must contain an __init__.py file where the database and schema names are defined
as global variables.
example for database:
# database1/__init__.py
global_string_database_name = "database1" # mandatory: database name
example for schema:
# database1/schema1/__init__.py
global_string_schema_name = "schema1" # mandatory: schema name
defining tables in tables.py
each schema folder must contain a tables.py file where:
- you must declare a Base object tied to the schema.
- you can define table classes, extending the Base object.
example tables.py:
# tables.py
from sqlalchemy import Column, Integer, String, MetaData
from sqlalchemy.ext.declarative import declarative_base
from square_database_structure.square.public import global_string_schema_name
# 1. mandatory: declare Base with metadata pointing to the schema
Base = declarative_base(metadata=MetaData(schema=global_string_schema_name))
# 2.optional: define table classes by extending Base
class App(Base):
__tablename__ = 'app'
id = Column(Integer, primary_key=True)
app_name = Column(String, nullable=False)
defining data in data.py
- you must declare a data_to_insert list to store optional data that may be inserted into the schema's tables.
from square_database_structure.square.public.tables import App
# 1. mandatory: initialize a list for optional data insertion
data_to_insert = []
# optional: append data to be inserted into the table
data_to_insert.append(App(app_name="example_app"))
defining function or stored procedure in stored_procedures_and_functions package
- paste this logic in the
__init__.pyof this package to discover all sql files.
from pathlib import Path
directory = Path(__file__).parent
stored_procedures_and_functions = []
for file_path in directory.iterdir():
if file_path.is_file() and file_path.suffix == ".sql":
with file_path.open("r") as file:
content = file.read()
stored_procedures_and_functions.append(content)
- you can keep raw sql files each containing ideally 1 stored procedure or function.
- the name of the file should ideally correspond to the function / procedure name.
- this raw sql should be compatible with postgres database.
CREATE OR REPLACE FUNCTION add_user(
p_username VARCHAR,
p_email VARCHAR
) RETURNS TEXT AS $$
BEGIN
-- Insert a new user into the users table
INSERT INTO users (username, email)
VALUES (p_username, p_email);
-- Return a success message
RETURN 'User added successfully!';
END;
$$ LANGUAGE plpgsql;
centralized definitions in main.py
the main.py file is mandatory and contains a global list that maps databases to schemas and their corresponding table definitions. this list is manually created by the user (for now).
example main.py:
# main.py
from square_database_structure.square.public import global_string_schema_name as schema1_name
from square_database_structure.square.public.tables import Base as Schema1Base
from square_database_structure.square.public.data import data_to_insert as schema1_data
from square_database_structure.square.public.stored_procedures_and_functions import (
stored_procedures_and_functions as schema1_stored_procedures_and_functions)
from square_database_structure.square import global_string_database_name as database1_name
# global list that maps databases and schemas
global_list_create = [
{
"database": database1_name, # mandatory: database name
"schemas": [
{
"schema": schema1_name, # mandatory: schema name
"base": Schema1Base, # mandatory: base for this schema
"data_to_insert": schema1_data, # mandatory: data to insert (even if empty)
"stored_procedures_and_functions": schema1_stored_procedures_and_functions,
# mandatory: stored procedures and functions (even if empty)
},
],
}
]
this file centralizes the definition of each database and schema, including the associated Base and data_to_insert for table definitions.
creating tables
once you have defined your databases, schemas, and tables, you can create them in your PostgreSQL database by using the
create_database_and_tables function.
from square_database_structure import create_database_and_tables
# define the database connection details
db_username = "your_username"
db_password = "your_password"
db_ip = "localhost"
db_port = 5432
# call the function to create the database and tables
create_database_and_tables(db_username, db_password, db_ip, db_port)
env
- python>=3.12.0
- postgresql >= 13
feedback is appreciated. thank you!
Metadata
Release files for square_database_structure 2.8.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| square_database_structure-2.8.1.tar.gz | 8.1 kB | Without provenance | Details for square_database_structure-2.8.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| square_database_structure-2.8.1-py3-none-any.whl | Python 3 | none | any | Details for square_database_structure-2.8.1-py3-none-any.whl |
Total release size: 27.7 kB
Release files / square_database_structure-2.8.1.tar.gz
| Download URL | square_database_structure-2.8.1.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
35310d7cb9f03e8e261e6eec27426a0ae0f9cd5a2767d35c431a5e0f826f2fdf
|
|
BLAKE2b-256 checksum How to use checksums |
6e789788445e92202779b3fd8c3b79b3d757ee49b0fc405360a437b1b936d3b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.12 {"installer":{"name":"uv","version":"0.10.12","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / square_database_structure-2.8.1-py3-none-any.whl
| Download URL | square_database_structure-2.8.1-py3-none-any.whl |
|---|---|
| Size | 19.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc664a650bdfdca259065f3bb69d4d405db7e68373d5ef7dab8acf994acbb3a0
|
|
BLAKE2b-256 checksum How to use checksums |
bb8872954bd7e5fb7b1bae7d9881fa039d53f084f1bf7892df8ae6416af0cc47
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.12 {"installer":{"name":"uv","version":"0.10.12","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for square_database_structure 2.8.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.