Changeset 5c20c64

Timestamp:

02/10/26 14:02:45 (5 months ago)

Author:

Andrej <asumanovski@…>

Branches:

master

Children:

ff01f66

Parents:

8615885

Message:

Added new content to the landing page and fixed app properties

Files:

• backend/src/main/resources/application.properties (modified) (2 diffs)
• db-scripts/dml.sql (modified) (7 diffs)
• frontend/src/pages/LandingPage/components/Benefits.jsx (added)
• frontend/src/pages/LandingPage/components/Features.jsx (added)

backend/src/main/resources/application.properties

@@ -4 +4 @@
 # JPA & Hibernate
 # ============================
-spring.jpa.hibernate.ddl-auto=update
+# NOTE: On some managed PostgreSQL providers the app user cannot read pg_catalog views
+# like pg_settings. Hibernate schema migration/metadata introspection can trigger that
+# access during startup (e.g., when ddl-auto=update).
+#
+# Default to no automatic DDL. Override locally if your DB user has sufficient rights:
+#   export SPRING_JPA_HIBERNATE_DDL_AUTO=update
+spring.jpa.hibernate.ddl-auto=${SPRING_JPA_HIBERNATE_DDL_AUTO:none}
 spring.jpa.properties.hibernate.dialect=org.hibernate.dialect.PostgreSQLDialect
 spring.jpa.show-sql=false
@@ -10 +16 @@
 spring.jpa.properties.hibernate.default_schema=trekr
 spring.jpa.properties.hibernate.hbm2ddl.create_namespaces=true
+
+# Avoid JDBC metadata access on boot (further reduces pg_catalog permission requirements)
+spring.jpa.properties.hibernate.boot.allow_jdbc_metadata_access=false
 
 # ============================

db-scripts/dml.sql

@@ -33 +33 @@
 (30, 'vlado@example.com', 'vlado_ilievski', '1234');
 
--- If USERS.user_id is an IDENTITY column, ensure its backing sequence is advanced
--- past the inserted dummy ids so future inserts (e.g., app registration) don't
--- try to reuse ids and fail with duplicate key errors.
 SELECT setval(
         pg_get_serial_sequence('trekr.users', 'user_id'),
@@ -109 +106 @@
 (39, 25, '2026-03-28', 6050);
 
--- If INCOMES.income_id is an IDENTITY column, advance its sequence past dummy ids.
 SELECT setval(
         pg_get_serial_sequence('trekr.incomes', 'income_id'),
@@ -191 +187 @@
 (30, 20, 2300, '2026-02-10');
 
--- If DAILY_INTAKES.daily_intake_id is an IDENTITY column, advance its sequence past dummy ids.
 SELECT setval(
         pg_get_serial_sequence('trekr.daily_intakes', 'daily_intake_id'),
@@ -223 +218 @@
 (24, 17, 17, 40, 320, '2026-02-13', 'Strength');
 
--- If TRAINING_SESSIONS.training_id is an IDENTITY column, advance its sequence past dummy ids.
 SELECT setval(
         pg_get_serial_sequence('trekr.training_sessions', 'training_id'),
@@ -263 +257 @@
 (15, 20, 'Exam Prep', 3, '["Practice","Mock","Review"]');
 
--- If CUSTOM_TRACKING_CATEGORIES.custom_tracking_id is an IDENTITY column, advance its sequence past dummy ids.
 SELECT setval(
         pg_get_serial_sequence('trekr.custom_tracking_categories', 'custom_tracking_id'),
@@ -331 +324 @@
 (60, 'Review Exam', FALSE, NULL, 15);
 
--- If TASKS.task_id is an IDENTITY column, advance its sequence past dummy ids.
 SELECT setval(
         pg_get_serial_sequence('trekr.tasks', 'task_id'),
@@ -430 +422 @@
 (17, 15, 'NVDA', 640, '2026-02-10', 0.9);
 
--- If ASSETS.asset_id is an IDENTITY column, advance its sequence past dummy ids.
 SELECT setval(
         pg_get_serial_sequence('trekr.assets', 'asset_id'),