Issue 60737 - Default values in slave form broken for first row inserted
Summary: Default values in slave form broken for first row inserted
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0
Hardware: PC Linux, all
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: dbaneedsconfirm
QA Contact: issues@dba
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2006-01-18 01:01 UTC by kieser
Modified: 2007-04-03 17:15 UTC (History)
1 user (show)

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


Attachments
Bzip2 compressed file of a plain text pg_dump for creating invoices database (5.03 KB, application/octet-stream)
2006-01-20 13:50 UTC, kieser
no flags Details
Sample OObase showing bug. Form to open is "csutomerMaintenance". Requires "invoices" db (see previous attachment and bug comments) (69.04 KB, application/vnd.sun.xml.base)
2006-01-20 13:52 UTC, kieser
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description kieser 2006-01-18 01:01:07 UTC
In a slave form, defaulting doesn't work properly with first row that is
automatically inserted when this is a column that has a dropdown based on a
query. If this is marked "not null with default" in the database, then an error
occurs once the first colmn value has been entered. When the master has a new
row added the slave therefore has a first row automatically inserted. The
default value is not populated in the column and hence an error results from the
form validation. E.g. A non-nullable country column that has a dropdown based on
a qry with the linked field being numeric (country code) and the displayed
column in the dropdown a string (country name). Should be able to specify a
default value that is automatically assigned when a new row is created. The
"default selection" does not work with the first row. It works okay if you
change it to nullable with default.
Comment 1 Frank Schönheit 2006-01-20 13:22:01 UTC
Do ease reproducing this issue, do you mind attaching a small sample database,
with a sample form? That's far easier for every party which is later involved
with this issue. Thanks for consideration.
Comment 2 kieser 2006-01-20 13:50:34 UTC
Created attachment 33408 [details]
Bzip2 compressed file of a plain text pg_dump for creating invoices database
Comment 3 kieser 2006-01-20 13:52:31 UTC
Created attachment 33409 [details]
Sample OObase showing bug. Form to open is "csutomerMaintenance". Requires "invoices" db (see previous attachment and bug comments)
Comment 4 kieser 2006-01-20 13:57:20 UTC
I have attached two files -

invoice.pgdump.txt.bz2 is a bzip2 file that should be uncompressed. The
uncompressed file is a plain text dump for PostgreSQL 8.0.0 that can be used to
recreate the "invoices" database so that you can use the OO2 Base docutment.

OO2PGInvoiceDB.odb is the OO2 Base document with the form that shows the bug.
The form name is "customerMaintenance".

The create the invoices DB follow these steps on a machine which PostgreSQL
8.0.0 installated:

create_db invoices
psql invoices < invoice.pgdump.txt

You may want to create a user and set the password for OO2 to connect to PG but
depending on your setup, this may already be in place or may not be needed.
Comment 5 kenwong 2006-09-23 16:17:17 UTC
Same problem with Base + MySQL.

http://www.oooforum.org/forum/viewtopic.phtml?t=30779
Comment 6 christoph.lukasiak 2006-10-25 15:33:03 UTC
1. does the problem still occure in current version (is this issue still alive)
2. my you write a step by step description for better repro - i am not shure,
that i do the same like you
3. may you attach a sample native (hsql) database for better repro (postgres &
driver make a of lot trouble on my test machines)

thx
Comment 7 christoph.lukasiak 2006-10-25 15:34:27 UTC
set keyword 'needmoreinfo'
Comment 8 kieser 2006-10-25 15:42:47 UTC
It certainly does! I will get a HSQL version of the DB for you to use.
Comment 9 christoph.lukasiak 2007-01-16 13:51:16 UTC
clu -> kieser: is that issue still alive or does it work now?
Comment 10 christoph.lukasiak 2007-04-03 17:14:09 UTC
no further respond -> seems to be fixed in between
Comment 11 christoph.lukasiak 2007-04-03 17:15:04 UTC
do not hestitate to reopen this issue if it still occurs in a current version
and you want to add a comment for better reproducebility

thx