To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=52919


User wurzel changed the following:

                  What    |Old value                 |New value
================================================================================
            Ever confirmed|                          |1
--------------------------------------------------------------------------------
                    Status|UNCONFIRMED               |NEW
--------------------------------------------------------------------------------
                  Keywords|needmoreinfo              |oooqa
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Thu Sep 15 10:45:12 -0700 
2005 -------
Here's more info and testing from a third person, confirming the behaviour. I'm
enclosing a link to the sample ODB file as well :

http://www.ktb.net/~jelly/ooo_db/delroute.odb

Alex

James, Alex, et al

I took the liberty of downloading the database and ran a little test.

What I did was first do a SCRIPT command on the database to see what HSQLDB
thought it had for table definitions. Then I created the following text file and
applied it to the databae via the SQL window in Base.

CREATE CACHED TABLE "Customers2"(
"Key" INTEGER GENERATED BY DEFAULT AS IDENTITY(START WITH 0) NOT NULL PRIMARY 
KEY,
"Number" VARCHAR(8) NOT NULL,
"Unit" VARCHAR_IGNORECASE(5),
"Street" VARCHAR_IGNORECASE(15),
"Prefix" VARCHAR_IGNORECASE(1),
"Suffix" VARCHAR_IGNORECASE(4),
"DeliverySegment" VARCHAR(20),
"SwitchSide" BOOLEAN DEFAULT FALSE NOT NULL ,
"DeliverySchedule" VARCHAR(3),
"Active" BOOLEAN DEFAULT TRUE NOT NULL,
"Ordinal" TINYINT,
"Last" BOOLEAN DEFAULT FALSE,
"Corner" BOOLEAN DEFAULT FALSE,
"Bag" BOOLEAN DEFAULT FALSE NOT NULL,
"Porch" BOOLEAN DEFAULT FALSE NOT NULL,
"Handicapped" BOOLEAN DEFAULT FALSE NOT NULL,
"SatSunonMon" BOOLEAN DEFAULT FALSE NOT NULL,
"Remark" VARCHAR(30),
"Sequence" VARCHAR(5),
"Order" SMALLINT NOT NULL)

Then creaed a second script file form the database to see if the two tables
Customers and Customers2 would indeed be different. Here are the results

CREATE CACHED TABLE "Customers"("Key" INTEGER GENERATED BY DEFAULT AS
IDENTITY(START WITH 0) NOT NULL PRIMARY KEY,"Number" VARCHAR(8) NOT NULL,"Unit"
VARCHAR_IGNORECASE(5),"Street" VARCHAR_IGNORECASE(15),"Prefix"
VARCHAR_IGNORECASE(1),"Suffix" VARCHAR_IGNORECASE(4),"DeliverySegment"
VARCHAR(20),"SwitchSide" BOOLEAN NOT NULL,"DeliverySchedule" VARCHAR(3),"Active"
BOOLEAN NOT NULL,"Ordinal" TINYINT,"Last" BOOLEAN,"Corner" BOOLEAN,"Bag" BOOLEAN
NOT NULL,"Porch" BOOLEAN NOT NULL,"Handicapped" BOOLEAN NOT NULL,"SatSunonMon"
BOOLEAN NOT NULL,"Remark" VARCHAR(30),"Sequence" VARCHAR(5),"Order" SMALLINT NOT
NULL)


CREATE CACHED TABLE "Customers2"("Key" INTEGER GENERATED BY DEFAULT AS
IDENTITY(START WITH 0) NOT NULL PRIMARY KEY,"Number" VARCHAR(8) NOT NULL,"Unit"
VARCHAR_IGNORECASE(5),"Street" VARCHAR_IGNORECASE(15),"Prefix"
VARCHAR_IGNORECASE(1),"Suffix" VARCHAR_IGNORECASE(4),"DeliverySegment"
VARCHAR(20),"SwitchSide" BOOLEAN DEFAULT false NOT NULL,"DeliverySchedule"
VARCHAR(3),"Active" BOOLEAN DEFAULT true NOT NULL,"Ordinal" TINYINT,"Last"
BOOLEAN DEFAULT false,"Corner" BOOLEAN DEFAULT false,"Bag" BOOLEAN DEFAULT false
NOT NULL,"Porch" BOOLEAN DEFAULT false NOT NULL,"Handicapped" BOOLEAN DEFAULT
false NOT NULL,"SatSunonMon" BOOLEAN DEFAULT false NOT NULL,"Remark"
VARCHAR(30),"Sequence" VARCHAR(5),"Order" SMALLINT NOT NULL

Then I created a NEW database and attempted to set the default values for the
boolean fields via the GUI. I am having the same problem with the defaults not
holding. In fact when I saved a table definition, then opened it for editing
again I could not save back, instead I received error messages as described in
Issue #52919. The behavior is identical to what is described in the closed Issue
#48851.

All my tests where done on WinXP SP2, Java JRE 1.5.0_04 and OO.o Build 1.9.129

Looks to me the problem is in the GUI of OO.o.

James, looks like the best way to get your tables right for now is via good old
ASCII issued to the database engine, shouldn't look to foriegn to an old
mainframer... ;-) 

Drew Jensen

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to