Issue 114280 - PostreSQL subforms broken with ODBC, JDBC
Summary: PostreSQL subforms broken with ODBC, JDBC
Status: CLOSED DUPLICATE of issue 113631
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 3.2.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: dbaneedsconfirm
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-03 00:47 UTC by peterdines
Modified: 2010-11-19 12:59 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description peterdines 2010-09-03 00:47:33 UTC 
Subforms do not work with PostgreSQL in OOo 3.2.1 using ODBC or JDBC - the subform does not show any 
records and it is impossible to edit information in the subform table grid. This occurs on Mac and 
Windows.
Comment 1 drewjensen.inbox 2010-09-03 05:45:33 UTC 
@peterdines Which version of Postgres are you connecting up to? Also, I'm
changing the priority on this down to a P3 for the moment, as it A) Looks like
the same issue found in another connector and already fixed. I don't have a
Postgres server that I can connect to at the moment, but will reset things
tomorrow and bring one up. Will check both 3.2.1 and the 3.3 developer release
at that time.
Comment 2 peterdines 2010-09-03 12:57:10 UTC 
This was with both the 9.0 rc1 and 8.4.4 stable versions. Thanks for looking into this so promptly!
Comment 3 peterdines 2010-09-03 16:14:55 UTC 
As per a user comment on a forum, I verified that PostreSQL JDBC subforms DO work properly in OOo 
3.1.1
Comment 4 peterdines 2010-09-04 02:37:26 UTC 
Same flaw affects H2 database with JDBC - cannot display, edit or add subform data with OOo 3.2.1
Comment 5 peterdines 2010-09-11 17:54:09 UTC 
Tried Postgres with JDBC and the OOo 3.3 beta on Windows - here's the error message (at least there 
WAS an error message this time!)

The data content could not be loaded.

SQL Status: 22023

The column index is out of range: 1, number of columns: 0.

The SQL command leading to this error is:

SELECT * FROM "public"."orderdetails" WHERE ( "orderid" = :link_from_orderid )
Comment 6 peterdines 2010-09-30 02:44:14 UTC 
Sort of resolved - I fixed it by going into advanced JDBC connection settings in Base and ticking "replace 
named parameters with '?' ". It appears that version 3.1.1 had this set by default, which is why it didn't 
exhibit this problem.

Ticking the control fixes the subform issue with Postgres and H2. I recommend that the default be 
changed back in future releases.
Comment 7 r4zoli 2010-11-19 12:58:34 UTC 
Possibly this is duplicate of issue 113632

*** This issue has been marked as a duplicate of 113631 ***
Comment 8 r4zoli 2010-11-19 12:59:10 UTC 
Duplicate -> Closing.