-
Notifications
You must be signed in to change notification settings - Fork 134
Update PostgreSQLEnhanced to v1.7.3 #781
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: maintenance/gramps60
Are you sure you want to change the base?
Update PostgreSQLEnhanced to v1.7.3 #781
Conversation
3b9bc32 to
b261307
Compare
|
Hi, Could someone review this please? Thanks! |
3fe53b9 to
a2cd046
Compare
Major update with dual backend registration and ConfigManager integration. Changes: - Dual backend registration: Monolithic and Separate modes - ConfigManager integration for per-tree settings.ini - Gramps 6.0.6 API compatibility (json_extract_expression, composite index) - Import guard for psycopg dependency checking - Bug fixes for config loading and database creation - Migration scripts for existing users - Documentation updates for Windows AIO and Flatpak Breaking changes: - Backend IDs changed to postgresqlenhanced-monolithic/separate - Migration scripts provided in scripts/ directory - Users must run migrate_to_dual_backends.py and migrate_to_settings_ini.py Fixes GitHub issues gramps-project#1 and gramps-project#2
a2cd046 to
c6c4ba2
Compare
|
Are you satisfied with the review such that this is ready for merge? |
|
Yes, I'm sorry. I was engrossed in other projects. Please merge. |
|
Tried to publish but failed. Something wrong with the GPR file. The publish step:
generates the json listing files, but does not include the 2 for this addon. If I take out the pre-register code in the latest GPR (as below), it will publish. Note: I added the requires_mod and audience fields from the previous version. Please fix the GPR file as needed so that it will publish. |
Update PostgreSQLEnhanced to v1.7.3
Summary
Major update to PostgreSQLEnhanced addon with dual backend registration, ConfigManager integration, and Gramps 6.0.6 API compatibility.
Key Changes
Dual Backend Registration
Mode selection now integrated into backend choice - users select the appropriate backend when creating a tree.
ConfigManager Integration
settings.inifiles following standard Gramps patternGramps 6.0.6 API Compatibility
json_extract_expression()method (required by DBAPI changes from Aug 2025)person_name_compositeindex for improved performanceBug Fixes
Migration for Existing Users
Two migration scripts provided in scripts/ directory:
Users upgrading from v1.5.2 should run both scripts.
Testing
Documentation
Breaking Changes
postgresqlenhancedtopostgresqlenhanced-monolithicandpostgresqlenhanced-separateCompatibility
Related