Issue 128092 - every standalone writer form-subform with postgresql produce syntax error log on load and at each refresh
Summary: every standalone writer form-subform with postgresql produce syntax error log...
Status: CLOSED DUPLICATE of issue 113494
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 4.1.6
Hardware: All All
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2019-04-16 05:55 UTC by Ansari
Modified: 2019-04-16 13:35 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Ansari 2019-04-16 05:55:42 UTC
I am running an application using postgresql with standalone writer forms with base. I started this at the very early stages of OO (infact started with Staroffice 5.2) migrated and moved up. I am stuck at OO 3.1.1 as from OO 3.1.2 sdbc driver available (0.7.6b) produced a syntax error on postgresql log on every form-subform link at load and with each refresh. My application uses from-subform link heavily and my postgresql-log gets filled up rapidly and became useless. This behaviour is same both windows and linux. since I need the postgresql-logs so stayed back at 3.1.1.

Now after many years LibreOffice 6.2 did some changes in that postgresql-sdbc-driver part to correct this postgresql log and that fix has been backported 6.1's. I did the test and YES it works. For sentimental reasons I prefer to stay with OO until
LO bundle the postgresql-sdbc driver, so cant install as an extension with openoffice

Would anyone please update that sdbc driver for postgresql, which is pretty old,
0.7.6b (released 2010-08-12). Or better bundle that LO's  postgresql sdbc driver with Apache openoffice in future.

Thank you all for the great work over the years.
Best Regards
Comment 1 Peter 2019-04-16 06:32:57 UTC
In order OpenOffice can adapt the developer who did this needs to acknowledge that the patch is released with APL2 License. LO use a different license model mixing our code in.

However we have build in postgres support, the version is just instable and not yet ready for production.
We are about to release a developer build for testing.
If you volunteer you could help to test our new postgres support.
Comment 2 oooforum (fr) 2019-04-16 07:43:51 UTC
Already reported

*** This issue has been marked as a duplicate of issue 113494 ***