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.
Build ID: a799d7c9a66464f33bd8ee42d535e29a976d64ae
Locale : fr-FR (fr.UTF-8)
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).
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>&)
message: Violation of unique constraint SYS_CT_64: duplicate value(s) for column(s) "NOME" in statement [INSERT INTO "Tabella1" ( "NOME") VALUES ( ?)]
On pc Debian x86-64 with LO Debian package 126.96.36.199 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 188.8.131.52 or with recent master sources?
(In reply to Julien Nabet from comment #4)
> On pc Debian x86-64 with LO Debian package 184.108.40.206 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 220.127.116.11 or with recent master sources?
Bug has disappeard with LO 5.0.* - don't know the version, have only tested with LO 18.104.22.168 and with LO 22.214.171.124.
If you open the form of the attached database and try to insert "max" in the tablecontrol, an errormessage appears in LO 126.96.36.199, doesn't appear in LO 188.8.131.52.
Should we set this to WORKSFORME?
It seems to be the same reason as bgu75340.
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)