https://bugs.documentfoundation.org/show_bug.cgi?id=147582

            Bug ID: 147582
           Summary: PostgreSQL JDBC: Form with Subform and SubSubform
                    gives Parameter Error for SubSubForm
           Product: LibreOffice
           Version: 7.3.0.3 release
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Base
          Assignee: [email protected]
          Reporter: [email protected]

Created attachment 178443
  --> https://bugs.documentfoundation.org/attachment.cgi?id=178443&action=edit
Pachage with SQL-code for tables and 2 form (direct and JDBC connection)

There are some more bugs about PostgreSQL and subforms. This is a bug special
for forms, which will contain a MainForm, a SubForm and a SubSubForm (subform
of the subform).

Download the attached package, which contains SQL-Code for creating 3 Tables in
PostgreSQL and fill on of the tables with first data.

Connect the database files to PostgreSQL. One file should be connected directly
with internal driver, the other through JDBC. You only have to change the
connection string in Edit → Database → Connection Type.

Open the form with direct connection. Will open without problems.

Open the form with JDBC. Will throw an error, because there seem to be
something with integer and varchar values …
Type an ID for the town and a town in the subform.
You couldn't type somethin in the subsubform, because it isn't connected to the
subform.
Close the form, reopen the form.
Now you could add data to the subsubform, special a name for the person.

This behavior could only be worked arround by connecting to a field, which is
defined as Varchar like:
SELECT "tbl_Person".*, CAST( "ID" AS VARCHAR ( 10 ) ) AS "ID2" FROM
"tbl_Person"
And get the value for the connected field for new rows by macro code from the
subform.

Tested with LO 7.3.1.1 on OpenSUSE 15.3 64bit rpm Linux

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to