Howdy folks,

*HJELP!* While experimenting with the a relationship problem , I think I
might have fudged the database. I've set up a 1:1 relationship between
two tables, cascading updates and so on. Now I can't access anything
anymore. This is the error I get:

Quote:

SQL-Status: S1000
Fehler-Code: -78

error in script file line: 10 Column types do not matchmissing DEFAULT
value on column HH-ID in statement [CREATE CACHED TABLE "Boxen"("HH-ID"
INTEGER NOT NULL PRIMARY KEY,"Tekguy" VARCHAR(50),"Box-ID"
INTEGER,CONSTRAINT SYS_FK_113 FOREIGN KEY("HH-ID") REFERENCES
"Haushalte"("HH-ID") ON DELETE SET DEFAULT ON UPDATE CASCADE]


All I want to do now is undo this relation, but I can't even open that
window without that error popping up. What can I do now? I would
consider deleting one of the two tables (although I can't seem to access
anything but the forms view...) if that would help... *HJELP*

cheers, Berti

P.S. And to think that this morning I actually pondered making a backup
and then didn't...

Berti Ferranti wrote:
The error message you posted is a little mangled, but it seems to be complaining about
the ON DELETE SET DEFAULT on the FOREIGN KEY constraint. "HH-ID" doesn't define a
default value.

However, it doesn't make much sense to use SET DEFAULT on a column that is also a
primary key. This would likely cause duplicate values for "HH-ID", breaking the PRIMARY
KEY uniqueness constraint.

I can't 'hjelp' you with opening that window ... whatever that means.

--
Lee Fesperman, FFE Software, Inc. (http://www.firstsql.com)
================================================== ============
* The Ultimate DBMS is here!
* FirstSQL/J Object/Relational DBMS (http://www.firstsql.com)

Lee Fesperman schrieb:
That's odd, since I didn't set a default for household ID. At least not
in the main table... The error message is an exact copy&paste of OOo's
output.

It means I need to undo creating that relationship despite the fact that
OOo refuses me me a connection to the database with the error above.
Any way to directly influence the script?

cheers, Berti

Berti Ferranti wrote:
The main table doesn't matter (assuming you mean the primary key table - "Haushalte").
The SET DEFAULT in the ON effects clause of a Foreign Key Constraint affects the table
containing the Constraint and the FK column ("HH-ID" in "Boxen"). The declaration for
the column - "HH-ID" in "Boxen", doesn't have a DEFAULT clause, so the error could be
saying that you can't specify SET DEFAULT on a column without a DEFAULT clause.
However...

The error message is mangled because of the word - 'matchmissing'. It also seems to be
saying there is a type match error. Does "HH-ID" in "Boxen" have the same type as
"HH-ID" in "Haushalte"? That is, the error message doesn't make sense.

I think you need to fix the error? in the CREATE TABLE. I'm assuming that the CREATE
TABLE is being processed as part of the connection, thus you need to change the
connection script.

I didn't know what 'OOo' meant, but Google suggests that it is OpenOffice.org.
OpenOffice supports multiple database backends. Which one are you using?

--
Lee Fesperman, FFE Software, Inc. (http://www.firstsql.com)
================================================== ============
* The Ultimate DBMS is here!
* FirstSQL/J Object/Relational DBMS (http://www.firstsql.com)