Loading request...
User requests that the authenticated user be stored in core models (like core_feeding) to enable tracking of which user performed a specific action, useful for multi-user environments.
I poked around in the SQLite database for how Baby Buddy stores some of its data. Here's an example of a typical model (feedings): ``` CREATE TABLE IF NOT EXISTS "core_feeding" ( "id" integer NOT NULL PRIMARY KEY AUTOINCREMENT, "end" datetime NOT NULL, "duration" bigint NULL, "type" varchar(255) NOT NULL, "method" varchar(255) NOT NULL, "amount" real NULL, "child_id" integer NOT NULL REFERENCES "core_child" ("id") DEFERRABLE INITIALLY DEFERRED, "notes" text NULL, "start" datetime NOT NULL ); ``` I noticed that there's no reference to *who* recorded the feeding. In general, it looks like Baby Buddy uses the auth users for authentication/authorization only but then doesn't record the effective user ID for activities. Here's the `auth_user` table: ``` CREATE TABLE IF NOT EXISTS "auth_user" ( "id" integer NOT NULL PRIMARY KEY AUTOINCREMENT, "password" varchar(128) NOT NULL, "last_login" datetime NULL, "is_superuser" bool NOT NULL, "username" varc