Bug 91975 - Missing Error Message in SQL-UNIQUE - Forms-mode
Summary: Missing Error Message in SQL-UNIQUE - Forms-mode
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
4.3 Daily
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-10 00:12 UTC by vlad
Modified: 2015-10-11 16:37 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
Just try to insert the word "max",in Table and Form views. (12.50 KB, application/vnd.sun.xml.base)
2015-06-10 00:12 UTC, vlad
Details

Note You need to log in before you can comment on or make changes to this bug.
Description vlad 2015-06-10 00:12:38 UTC
Created attachment 116432 [details]
Just try to insert the word "max",in Table and Form views.

When has executed the SQL-command "ALTER TABLE ADD UNIQUE ("MyColumn")" ,if trying to insert again the same value(Table mode),I got an error message.If I am switching to Forms mode,I receive no any message and it is impossible to save the new record,without any explanation.
Best regards
Comment 1 Alex Thurgood 2015-06-10 17:31:18 UTC
Confirming on

Version: 5.1.0.0.alpha1+
Build ID: a799d7c9a66464f33bd8ee42d535e29a976d64ae
Locale : fr-FR (fr.UTF-8)

OSX 10.10.3
Comment 2 Robert Großkopf 2015-06-10 17:58:04 UTC
This is an old problem - could be since OOo. Have a look at bug75340 - could be the same reason.

The error message appears if you press the button for saving the row (navigationbar).
Comment 3 Julien Nabet 2015-06-10 19:51:50 UTC
On pc Debian x86-64 with master sources updated yesterday, I could reproduce this.
If I click on button and confirm I want to save, I've got no error message.

If I click on Save button, I've got the message.

But for the first case, I noticed this on console:
warn:legacy.osl:3087:1:svx/source/form/formfeaturedispatcher.cxx:157: caught an exception!
in function:virtual void svx::OSingleFeatureDispatcher::dispatch(const com::sun::star::util::URL&, const com::sun::star::uno::Sequence<com::sun::star::beans::PropertyValue>&)
type: com.sun.star.sdbc.SQLException
message: Violation of unique constraint SYS_CT_64: duplicate value(s) for column(s) "NOME" in statement [INSERT INTO "Tabella1" ( "NOME") VALUES ( ?)]
Comment 4 Julien Nabet 2015-10-11 13:14:21 UTC
On pc Debian x86-64 with LO Debian package 5.0.2.2 or with master sources updated today, I don't reproduce this anymore (or don't remember the specific action to do?).
Could someone test again with 5.0.2.2 or with recent master sources?
Comment 5 Robert Großkopf 2015-10-11 16:22:53 UTC
(In reply to Julien Nabet from comment #4)
> On pc Debian x86-64 with LO Debian package 5.0.2.2 or with master sources
> updated today, I don't reproduce this anymore (or don't remember the
> specific action to do?).
> Could someone test again with 5.0.2.2 or with recent master sources?

Bug has disappeard with LO 5.0.* - don't know the version, have only tested with LO 5.0.3.1 and with LO 4.4.6.1. 
If you open the form of the attached database and try to insert "max" in the tablecontrol, an errormessage appears in LO 5.0.3.1, doesn't appear in LO 4.4.6.1.

Should we set this to WORKSFORME?
It seems to be the same reason as bgu75340.
Comment 6 Julien Nabet 2015-10-11 16:37:06 UTC
Thank you Robert for your feedback, let's indeed put this one to WFM since you reproduced it with LO version < 5.0 and not with LO version >= 5.0 + the fact that 4.4 branch is soon EOL (and so only most important bugs should be investigated)