lapa-database 0.0.12

database layer for my personal server.

lapa_database

about

database layer for my personal server.

installation

pip install lapa_database[all]

usage (WIP)

change password in config.ini.

CREATE_SCHEMA = True to create database from scratch.

LOG_FILE_NAME and configure logger

link to lapa_database_structure

config

lapa_database\data\config.ini

env

• python>=3.12.0

changelog

v0.0.12

• fix bug in reading log_file_name.

v0.0.11

• add square_logger section in environment and initialise logger as per those variables.
• keep logger and lapa_database_structure as >= instead of ~=.
• update minimum version for lapa_commons.

v0.0.10

• removed import for main file from config.
• removed validation for table names in crud call in pydantic models.
• adjust all crud calls to account for pydantic model change from enum to str.

v0.0.9

• removed config.example.ini.
• bug fix: create_database -> data insertion now takes schema into account.

v0.0.8

• add module name in config.
• add first test case.
• add dependencies for testing.
• add GitHub workflow for testing.
• remove config from gitignore.

v0.0.7

• use lapa_commons to read config.

v0.0.6

• change default value of ignore_filters_and_get_all to False.

v0.0.5

• make crud logic default to no rows when filters are empty.
• add new parameters to make it easy to select all rows for edit, delete and get.
• move logger to configuration.py to fix bug of multiple logs being created.

v0.0.4

• rename to lapa database.
• fix bug in create_database that occurred in default data insertion.
• add logs to gitignore.
• change psycopg2 to psycopg2-binary in setup.py.

v0.0.3

• created utils folder containing CommonOperations.py under which the common functions used across modules are stored.
• web_socket implemented for retrieving the data from the table when a new row is added/deleted/updated.
  • it takes database_name, table_name and schema_name as input through query params.
  • input for websocket
    • /ws/<database_name>/<table_name>/<schema_name>
      • E.g. /ws/game/player/public
  • initially returns all the rows and if any update is made it returns the updated data.
  • trigger creation is implemented once the websocket connection is made. it will first check if the trigger function already exists or not and then only create.

v0.0.2

• remove databases folder and enums related to tables and put in separate module for better version control.
• add proper error message display on errors in configuration.py.
• known bugs:
  • creating engines everytime on fastapi route call is creating idle sessions.

v0.0.1

• initial implementation.
• known bugs:
  • creating engines everytime on fastapi route call is creating idle sessions.

Feedback is appreciated. Thank you!