[dba-issues] [Issue 114304] Default not being set pro perly when creating a boolean field via SQL
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114304 --- Additional comments from atjen...@openoffice.org Sun Sep 5 03:21:36 + 2010 --- Created an attachment (id=71564) changed boolean field - and form control is set to tri-state true - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114304] Default not being set pro perly when creating a boolean field via SQL
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114304 --- Additional comments from atjen...@openoffice.org Sun Sep 5 03:18:34 + 2010 --- @villeroy - I can't do that here - using 3.2.1 (vanilla) on linux if I try to apply, using the SQL window, your example: ALTER TABLE BOOLS ADD COLUMN ABOOLS BOOLEAN DEFAULT NULL NOT NULL I get this result: 1: Attempt to insert null into a non-nullable column: column: ABOOLS table: BOOLS in statement [ALTER TABLE BOOLS ADD COLUMN ABOOLS BOOLEAN DEFAULT NULL NOT NULL] Which is correct. In fact here the only statement it will take, without a default setting is: ALTER TABLE BOOLS ADD ABOOL BOOLEAN And then yup your right - thee is no way to get a null with the form controls - or display a null atually it seems - attached another file - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114314] Base only retreives first result set when MySQL procedure returns multi ple result sets
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114314 Issue #|114314 Summary|Base only retreives first result set when MySQL proced |ure returns multiple result sets Component|Database access Version|OOO320m12 Platform|Unknown URL| OS/Version|Windows Vista Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|MySQL Connector/OOo Assigned to|dbaneedsconfirm Reported by|prune --- Additional comments from pr...@openoffice.org Sun Sep 5 02:09:08 + 2010 --- When I run a query that simply calls a MySQL stored procedure (I'm using ODBC) which returns multiple result sets, Base only displays the first result set. Using DataPilot in Calc to try to use the database as a source likewise only gets the first result set. - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114299] Error with some valid que ries
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114299 --- Additional comments from pr...@openoffice.org Sun Sep 5 02:03:57 + 2010 --- r4zoli, I'm using MySQL 5.01 running on a SUSE x64 machine, with OO running on a Vista x64 machine, using ODBC. The query runs in Base if I check the "Run SQL command directly" button. - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114304] Default not being set pro perly when creating a boolean field via SQL
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114304 --- Additional comments from ville...@openoffice.org Sat Sep 4 19:38:59 + 2010 --- In this context I discovered that any field type except Boolean can be defined as DEFAULT NULL NOT NULL. The grids and the forms will leave the field blank and Base will complain one way or the other when the user tries to store without filling the empty field. Try this with a boolean field. For a mandatory boolean field (NOT NULL) Base will always put a false False into the grid or form control respectively. - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114310] wrong reading from tables under windows 7 64 bit
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114310 Issue #|114310 Summary|wrong reading from tables under windows 7 64 bit Component|Database access Version|OOO320m18 Platform|All URL| OS/Version|Windows 7 Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|none Assigned to|dbaneedsconfirm Reported by|cglania --- Additional comments from cgla...@openoffice.org Sat Sep 4 17:00:06 + 2010 --- Hi, under windows XP, I created an ooo base database. In a simplified view, it contains families and persons. The family table has familiy number as key, the person table has a person number as key and a foreign key relation to the family number in the family table. Example table records are: Family Table: Family No family name 10 Smith 20 Miller Person Table Person no Family No Person name 101 10 John Smith 102 10 Lisa Smith 201 20 Henry Miller. As long as I used windows XP, this worked fine in all tables, forms, queries and reports. No I have a new PC with windows 7, 64 bit. When I open the existing database on the new PC, and display the content of the the person table, I get: Person no Family No Person name 101 10 John Smith 101 10 John Smith 201 20 Henry Miller. So instead of the recors 101 and 102, I get twice the record 101 (in spite of the primary key on the person no). The same error occurs in forms which display data from both tables, and in queries accessing the person table only. Deeply below the system still knows the correct data: I cannot create a second record with key 102 via a form, although the existing 102 record is not displayed. Only in queries which access both tables, the result is correct. - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114304] Default not being set pro perly when creating a boolean field via SQL
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114304 User atjensen changed the following: What|Old value |New value CC|'r4zoli' |'atjensen,r4zoli' - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114304] Default not being set pro perly when creating a boolean field via SQL
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114304 --- Additional comments from atjen...@openoffice.org Sat Sep 4 14:59:33 + 2010 --- Sorry for splitting posts - last paragraph(s) should be You can not enter record via the dataview without entering explicitly a value for the boolean field, and the controls do not pick up the default value - but that has always been true I think. In the form you can enter a record without touching the boolean field but then the, when you do so the record is set with a FALSE in the boolean field - BUT - this is because the checkbox field on the form is set to be for TRI-STATE = FALSE - with this setting it is not picking up the default setting from the database. If you open that form and change the setting for that control to TRI-STATE equals TRUE then the control will correctly pick up the default value TRUE and you see at runtime that it will not accept the NULL state, since the table does not accept it - try with a field set to default TRUE and don't add the NOT NULL and you will see the difference in the form is picked up. So there really are two issues here - one the checkbox control does not pickup the table default setting when tri-state = FALSE Two - the checkbox control in the dataview grid is not tri-state = TRUE At least that's how it looks to me. - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114304] Default not being set pro perly when creating a boolean field via SQL
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114304 --- Additional comments from atjen...@openoffice.org Sat Sep 4 14:47:51 + 2010 --- Created an attachment (id=71557) bog doc example - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114304] Default not being set pro perly when creating a boolean field via SQL
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=114304
--- Additional comments from atjen...@openoffice.org Sat Sep 4 14:46:26
+ 2010 ---
Using Ubuntu 10.04, OOo 3.2 (go-oo) and 3.2.1 (vanilla) I find no difference -
Inserts via direct SQL with a default setting is working.
Inserts via data controls under Base not working.
Open the attached file -
To see that SQL inserts are working open the SQL window and enter
INSERT INTO BOOLS ("Alpha") values ('yet another' )
After executing if you open the bools table or form you will see that the
inserted record has the default of TRUE set for the boolean field.
Now open either the table dataview or bools form and try to enter a new record -
you can do so without entering anything in the second "boolean" field - because
the setting on the datasource is set NOT to check for required fields, since the
boolean field is also defaulted NOT NULL.
-
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: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114304] Default not being set pro perly when creating a boolean field via SQL
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114304 --- Additional comments from anothera...@openoffice.org Sat Sep 4 14:41:58 + 2010 --- Based off the things Villeroy saw, I've opened another issue (http://www.openoffice.org/issues/show_bug.cgi?id=114309) that might be related to this one where Boolean fields created with NOT NULL that do not have a default value try to send NULL values when records are added. - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114309] NULL Boolean values being sent when NOT NULL specified in SQL Create Ta ble
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=114309
Issue #|114309
Summary|NULL Boolean values being sent when NOT NULL specified
| in SQL Create Table
Component|Database access
Version|OOo 3.2.1
Platform|Macintosh
URL|
OS/Version|Mac OS X
Status|UNCONFIRMED
Status whiteboard|
Keywords|
Resolution|
Issue type|DEFECT
Priority|P3
Subcomponent|none
Assigned to|dbaneedsconfirm
Reported by|anotheralan
--- Additional comments from anothera...@openoffice.org Sat Sep 4 14:36:52
+ 2010 ---
If a table is created directly from SQL with a Boolean field that is set to NOT
NULL, errors arise when trying to insert new records where no changes are made
to the field.
(Note: there is a related bug
"http://www.openoffice.org/issues/show_bug.cgi?id=114304"; where DEFAULT values
for booleans are not being set properly, but this addresses a case where no
Default value is defined, but NOT NULL is. According to the HSQLDB docs
"http://hsqldb.org/doc/guide/ch09.html#create_table-section"; this should be a
valid definition).
Editing the table, the boolean field initially appears in an unchecked/FALSE/No
state, but if no change is made to it, a NULL value is sent when attempting to
create the record. This causes an error as described below.
For a walkthru example:
>From the Tools->SQL... Menu, run the following to create a new table with a
boolean value set to NOT NULL:
CREATE TABLE "testTable" ("pKey" INTEGER IDENTITY PRIMARY KEY, "testBool"
BOOLEAN NOT NULL, "testText" VARCHAR(50));
Run the View->Refresh Tables option to see the update table.
In the "Tables" view, double click on the "testTable" to open it directly.
The "testBool" field shows up as unchecked/FALSE.
Enter some text in the "testText" field and hit return or tab to add the
record.
An error occurs saying:
Error inserting the new record
Attempt to insert null into a non-nullable column: column: testBool table:
testTable in statement [INSERT INTO "testTable" ("testBool", "testText") VALUES
(?,?)]
Toggle the testBool to checked/TRUE and then back to unchecked/FALSE and try to
insert the record again and it works as expected.
-
Opening the testTable in edit mode, the GUI presents the default value for
"testBool" as "No". However, this does not correspond with the behavior seen
above. If the Default value in the GUI is toggled to "Yes" and then back to "No"
and saved, data entry directly into the table as described above works as
expected with no errors. (Note, you may have to click out of the Default value
field after changing to "Yes" in order for it to be seen as a change.)
-
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: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114304] Default not being set pro perly when creating a boolean field via SQL
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114304 User r4zoli changed the following: What|Old value |New value CC|''|'r4zoli' Assigned to|dbaneedsconfirm |oj Ever confirmed| |1 Status|UNCONFIRMED |NEW OS/Version|Mac OS X |All Platform|Macintosh |All Target milestone|--- |OOo 3.x --- Additional comments from r4z...@openoffice.org Sat Sep 4 12:25:23 + 2010 --- I can confirm it in OOO330m6 on win7, changed OS, platform. I tested more with Villeroy example from: http://user.services.openoffice.org/en/forum/viewtopic.php?f=61&t=33816 CREATE TABLE "testTable" (ID INT PRIMARY KEY, "testBool" BOOLEAN DEFAULT TRUE NOT NULL); Opened table data view, added data, only into the ID filed. First record inserted default value, I used ID=1. Second record with ID=2 gives error: Error inserting the new record More on error: "SQL Status: 23000 Error code: -10 Attempt to insert null into a non-nullable column: column: testBool table: testTable1 in statement [INSERT INTO "testTable1" ( "ID","testBool") VALUES ( ?,?)]" No changes after closing reopening odb file, or restart OOo. Set target, assign developer. - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 96825] in base query format is no t memorized
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=96825 --- Additional comments from maurice_sta...@openoffice.org Sat Sep 4 11:12:03 + 2010 --- Created an attachment (id=71554) test file with formatted queries - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 96825] in base query format is no t memorized
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=96825 --- Additional comments from maurice_sta...@openoffice.org Sat Sep 4 11:13:21 + 2010 --- Created an attachment (id=71555) query_format_test.odb with queries' format lost - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 96825] in base query format is no t memorized
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=96825
User maurice_starck changed the following:
What|Old value |New value
OS/Version|Windows XP|Windows 7
--- Additional comments from maurice_sta...@openoffice.org Sat Sep 4
11:10:00 + 2010 ---
I created a small test file (query_format_test.obd) with one table and five
queries. I saved it, close it, re-opened it, added some entries, save it
again... without problem. But after several tests (open, add/modify entries,
save, close) the format of the last three queries disappeared!
I'll create two new attachments:
query_format_test.obd with formatted queries (I hope that the format will be
saved!)
and query_format_lost.obd with the lost format.
You may also notice that the choice made for the bottom right part of the window
("document") isn't memorized (always reset to "none"). Since I use the French
version the "..." might be slightly different.
-
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: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114304] Default not being set pro perly when creating a boolean field via SQL
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=114304
Issue #|114304
Summary|Default not being set properly when creating a boolean
| field via SQL
Component|Database access
Version|OOo 3.2.1
Platform|Macintosh
URL|
OS/Version|Mac OS X
Status|UNCONFIRMED
Status whiteboard|
Keywords|
Resolution|
Issue type|DEFECT
Priority|P3
Subcomponent|none
Assigned to|dbaneedsconfirm
Reported by|anotheralan
--- Additional comments from anothera...@openoffice.org Sat Sep 4 11:06:02
+ 2010 ---
Using OpenOffice 3.2.1 (Build: 9502) on Mac OSX 10.6.4.
When attempting to use a direct SQL Create Table statement to set a default
value for a boolean field (via the Tools->SQL menu), the field is created
properly, but the default does not get applied.
Based off the documentation here:
http://hsqldb.org/doc/guide/ch09.html#create_table-section
If this statement is run:
CREATE TABLE "testTable" ("testBool" BOOLEAN DEFAULT TRUE NOT NULL);
a new table should be created that has a "testBool" field the defaults to TRUE
(which would show up as "Yes" in the Base display). However, with the above
statement the default is actual set to FALSE (which shows up as "No" in the Base
display).
(Note: after running an SQL command to create a table, you need to run the
View->Refresh Tables menu option to see new tables.)
It does not appear that the default is being set improperly, but rather that the
default is being ignored all together.
For some further examples, running the following:
CREATE TABLE "testTableB" (
"pKey" INTEGER NOT NULL IDENTITY PRIMARY KEY,
"test01" BOOLEAN DEFAULT TRUE NOT NULL,
"test02" BOOLEAN DEFAULT True NOT NULL,
"test03" BOOLEAN DEFAULT true NOT NULL,
"test04" BOOLEAN DEFAULT 1 NOT NULL,
"test05" BOOLEAN DEFAULT FALSE NOT NULL,
"test06" BOOLEAN DEFAULT False NOT NULL,
"test07" BOOLEAN DEFAULT false NOT NULL,
"test08" BOOLEAN DEFAULT 0 NOT NULL,
"test09" BOOLEAN DEFAULT TRUE,
"test10" BOOLEAN DEFAULT True,
"test11" BOOLEAN DEFAULT true,
"test12" BOOLEAN DEFAULT 1,
"test13" BOOLEAN DEFAULT FALSE,
"test14" BOOLEAN DEFAULT False,
"test15" BOOLEAN DEFAULT false,
"test16" BOOLEAN DEFAULT 0
);
Will produce a table where all the fields with "NOT NULL" end up with a default
value of "No" regardless of if "TRUE" or "FALSE" was requested. Any fields
without the "NOT NULL" spec end up with a default of .
-
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: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114299] Error with some valid que ries
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114299 User r4zoli changed the following: What|Old value |New value Priority|P2|P3 --- Additional comments from r4z...@openoffice.org Sat Sep 4 07:31:46 + 2010 --- Set priority back to P3, according: http://qa.openoffice.org/scdocs/ddIssues_EnterModify.html#priority - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 114299] Error with some valid que ries
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114299 User r4zoli changed the following: What|Old value |New value CC|''|'r4zoli' --- Additional comments from r4z...@openoffice.org Sat Sep 4 07:24:16 + 2010 --- What version of MySQL you used and what happens if you use JDBC or ODBC connector instead of native driver? Works with OOo Base UI or you use "Run SQL commands directly" option? Can you upload some dump script? (if not sensitive) - 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
