Update PostgreSQLEnhanced to v1.7.3#781
Open
glamberson wants to merge 1 commit intogramps-project:maintenance/gramps60from
Open
Update PostgreSQLEnhanced to v1.7.3#781glamberson wants to merge 1 commit intogramps-project:maintenance/gramps60from
glamberson wants to merge 1 commit intogramps-project:maintenance/gramps60from
Conversation
3b9bc32 to
b261307
Compare
Author
|
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
Member
|
Are you satisfied with the review such that this is ready for merge? |
Author
|
Yes, I'm sorry. I was engrossed in other projects. Please merge. |
Member
|
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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