Bug 47468 - : EDITING - Default values not shown immediately when entering new data into a table
Summary: : EDITING - Default values not shown immediately when entering new data into ...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
3.5.1 release
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-18 00:59 UTC by hc.stoellinger
Modified: 2021-03-02 11:27 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hc.stoellinger 2012-03-18 00:59:15 UTC
When entering new tuples into my MySQL (5.1) database, default values are not shown immediately at "commit" of the tuple. Only when I refresh the view of the table do they appear correctly. Default values should be shown immediately after entry according to definitions in the CREATE TABLE SQL statement.
Comment 1 sasha.libreoffice 2012-06-12 02:30:47 UTC
Thanks for bugreport
Please, verify if in last version of LibreOffice still reproducible
Comment 2 hc.stoellinger 2012-06-12 03:45:24 UTC
Hello,
Yes, it still is wrong under 3.5.4 with ODBC. In fact, I had defined a date
column with a default of '1999-09-01'. When not entering any value LO fills
it with "03.01.1" which - because I live in Austria - probable means '2001-03-01'.
This value is shown even after refreshing the window.
Thanks for your help
Regards
H. Stoellinger



On Tue, 12 Jun 2012 11:30:47 +0200, <bugzilla-daemon@freedesktop.org> wrote:

> https://bugs.freedesktop.org/show_bug.cgi?id=47468
>
> sasha.libreoffice@gmail.com changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |sasha.libreoffice@gmail.com
>
> --- Comment #1 from sasha.libreoffice@gmail.com 2012-06-12 02:30:47 PDT ---
> Thanks for bugreport
> Please, verify if in last version of LibreOffice still reproducible
>
Comment 3 sasha.libreoffice 2012-06-12 04:03:59 UTC
@ H. Stoellinger
Thanks for additional testing

@ Lionel
Greetings
What do You think about this bug?
Comment 4 hc.stoellinger 2012-06-12 04:17:42 UTC
What do I think about this bug?
Well, as I mentioned before in the original bug report: It would DEFINITELY
prevent me from using LO in a business environment. I used to look after
large customers at IBM. They sometimes had to write something like 200.000
letters to customers. This could NEVER be done if every single letter was
going to have to be done separately... NO GO!!
Regards
H. S.

On Tue, 12 Jun 2012 13:03:59 +0200, <bugzilla-daemon@freedesktop.org> wrote:

> https://bugs.freedesktop.org/show_bug.cgi?id=47468
>
> --- Comment #3 from sasha.libreoffice@gmail.com 2012-06-12 04:03:59 PDT ---
> @ H. Stoellinger
> Thanks for additional testing
>
> @ Lionel
> Greetings
> What do You think about this bug?
>
Comment 5 sasha.libreoffice 2012-06-12 23:37:54 UTC
Sorry for misunderstanding. After character '@' we write name, to who we speaking. This question was for Lionel, our database expert.
Comment 6 Jochen 2012-08-25 20:32:00 UTC
@ Lionel,
@ Robert,

did not you already described this problem?
Comment 7 Robert Großkopf 2012-08-26 18:16:22 UTC
@Jochen,

it's a problem with external databases. With the internal HSQLDB the default of the GUI and the default created in SQL-mode works right. It is shown in the field after saving the data. 

I haven't tested it with an external database. Could be a problem of ODBC, when I read Comment 2 in the right way.
Comment 8 Jochen 2012-08-26 18:27:45 UTC
Hi H. Stoellinger,

please list the single steps (all) - from starting LibreOffice until your last step.
Creating screenshots concerning important steps/events would not be bad.

@all
IMHO subject must be changed ("... external database ...").
What do you think?
Comment 9 Robert Großkopf 2013-01-17 20:47:20 UTC
When I had a look at comment 2, I saw the default date as "03.01.1". There was a bug in LO 3.3 - https://bugs.freedesktop.org/show_bug.cgi?id=34410 - which shows the same result, when fields with a date were internal NULL.

How do you create this default-field?

I have now tested with LO 3.6.4.3 and 3.5.7.1 and ODBC-Connection under OpenSuSE Linux 32 bit rpm. No problem with default values of a date, when they are created directly in MySQL. 
With every connection to the database I saw the default-value directly after commit of data.
Problems with editing default values of a date, when they are created in the GUI of LO with the wrong formatting. Must be given like 2013-01-17. 
Default values in the GUI are not saved in the database. So this values appear when you create a new row before you commit.

I can't confirm this bug under linux. 
@hc.stoellinger: Does this behavior already exist under Linux with the actual LO 3.6.4.3?
Comment 10 Lionel Elie Mamane 2013-01-21 16:22:25 UTC
Can't reproduce, no information from submitter since more than six months, presuming fixed in some way. If somebody can reproduce on recent LibreOffice, reopen with precise reproduction instructions.

Here's what I did to test:

 LibreOffice 4.0 RC on Debian/GNU Linux amd64
 libmyodbc 5.1.10-2

$ mysql -uroot -p -hmysql.localnetwork
Server version: 5.1.66-0+squeeze1 (Debian)
mysql> CREATE DATABASE TMP;
mysql> use TMP
mysql> CREATE TABLE `TEST` (
  `ID` int(11) NOT NULL,
  `VAL` varchar(100) NOT NULL DEFAULT 'none',
  `dVal` datetime NOT NULL DEFAULT '1972-04-06 00:00:00',
  PRIMARY KEY (`ID`)
) ENGINE=MyISAM;

Then, connect in LibreOffice through ODBC; here's the DSN in ~/.odbc.ini:

[MySQL]
Description             = MySQL
Driver          = MySQL
Server          = mysql.localnetwork
Database                = TMP


Double-click on TMP/TEST.

Enter "1" in "ID" column, and press "down arrow". Works.
Enter "2" in "ID" column, and press "down arrow". Works.
Enter "3" in "ID" column and "three" in VAL column, and press "down arrow". Works.