Issue 117468

Summary: problem creating a form with a subform (in a more-to-more relationship) using tables on a database server, connected to OoBase by for example JDBC
Product: Base Reporter: koen
Component: codeAssignee: AOO issues mailing list <issues>
Status: UNCONFIRMED --- QA Contact:
Severity: Normal    
Priority: P3 CC: issues, r4zoli
Version: OOO330m20   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description koen 2011-03-19 12:14:18 UTC
Hi all,

I have a problem creating a form with a subform (in a more-to-more relationship) using tables on a database server, connected to OoBase by for example JDBC. I wanted to use OoBase as a frontend as I enjoy the fact that the primary form and the subform can be beautifully layouted as an Excel sheet! The table definitions I have used are shown below; when the tables are located in OoBase itself it works beautifully; I used JDBC, ODBC and SDBC to connect to MySQL as well as postgreSQL. The errors with the various components and databases differ but all seem related. I will show you one example: postgreSQL using JDBC.

Using the form wizard; in step 1 I select all columns of table recepten, in step 2 I select public.koppeltabel. In step 3 I select all columns of this table. Then I click finish.

Error message: The data content could not be loaded. The column index is out of range: 1, number of columns: 0.

Version postgreSQL: 9.0.

JDBC: postgresql-9.0-801.jdbc4.jar.

I hope this is not a duplicate or a specifically non-supported use of your system. Otherwise I hope more will benefit!

Many thanks in advance! Koen de Heer




CREATE TABLE recepten (
	id_recepten SERIAL PRIMARY KEY,
	naam_recepten VARCHAR(255) NOT NULL,
	aantalPersonen_recepten  INTEGER,
	recept_recepten TEXT,
);

CREATE TABLE ingredienten (
	id_ingredienten SERIAL PRIMARY KEY,
	naam_ingredienten VARCHAR(255) NOT NULL,
	eenheid_ingredienten VARCHAR(50) NOT NULL
);

CREATE TABLE koppeltabel (
	id_koppeltabel SERIAL PRIMARY KEY,
	idRecepten_koppeltabel INTEGER NOT NULL REFERENCES recepten(id_recepten),
	idIngredienten_koppeltabel INTEGER NOT NULL REFERENCES ingredienten(id_ingredienten),
	aantal_koppeltabel FLOAT
);
Comment 1 Oliver-Rainer Wittmann 2012-06-13 12:19:10 UTC
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.
Comment 2 r4zoli 2012-09-09 06:25:01 UTC
This bug is a general, not connected directly to MySQL connector OOo, change component to none.
Comment 3 r4zoli 2012-09-09 07:09:31 UTC
component -> none.