#84: Consistent handling of optional functionality
----------------------+-----------------
Reporter: cito | Owner:
Type: defect | Status: new
Priority: major | Milestone: 5.2
Component: C Module | Version: 5.0
Keywords: |
----------------------+-----------------
The way optional functionality is configured in PyGreSQL is problematic.
Also, using an old libpq with a PyGreSQL compiled against a newer libpq
creates "undefined symbol" errors when libpq functions do not exist in the
older libpq, even when they are not used. We need to investigate if there
is a solution that allows using older libpq versions with newer PyGreSQL
binaries, or create a "compatibility version" setting that allows building
PyGreSQL binaries compatible with older libpq versions.
See https://github.com/Cito/PyGreSQL/issues/12 for details and follow-up.
--
Ticket URL: <http://trac.pygresql.org:8000/pgtracker/ticket/84>
PyGreSQL <http://www.pygresql.org/>
PyGreSQL Tracker
_______________________________________________
PyGreSQL mailing list
PyGreSQL@Vex.Net
https://mail.vex.net/mailman/listinfo/pygresql
