[Libreoffice-bugs] [Bug 108058] After renaming Primary Key AutoValue feature fails

2022-12-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108058

--- Comment #8 from Robert Großkopf  ---
Bug ist still the same in LO 7.4.3.2 on OpenSUSE 15.3 64bit rpm Linux

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108058] After renaming Primary Key AutoValue feature fails

2022-12-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108058

--- Comment #7 from QA Administrators  ---
Dear Howard Johnson,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108058] After renaming Primary Key AutoValue feature fails

2020-12-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108058

--- Comment #6 from QA Administrators  ---
Dear Howard Johnson,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 108058] After renaming Primary Key AutoValue feature fails

2018-12-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108058

--- Comment #5 from oldironsides1...@hotmail.com ---
I submitted the following bug which may be related.

Bug 122300 - LibreOffice Base: Table Creation Wizard: Primary Key "AutoValue"
does not populate after error.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 108058] After renaming Primary Key AutoValue feature fails

2018-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108058

--- Comment #4 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 108058] After renaming Primary Key AutoValue feature fails

2017-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108058

rob...@familiegrosskopf.de changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||rob...@familiegrosskopf.de
 Ever confirmed|0   |1

--- Comment #3 from rob...@familiegrosskopf.de ---
The buggy behavior is:
You change the fieldname but
AutoValue will be shown in the editor and wouldn't be changed to "No".

When I save the table an will do
View > Refresh Tables
or close the database and reopen the database
the AutoValue has been changed for the changed field to "No".

You have only to set it back to "Yes" and save the table - works here.

Two solutions for this:
1. When changing a fieldname (not deleting!) fieldtype and AutoValue shouldn't
be changed.
2. When changing the fieldname and AutoValue will be changed by this command,
it should be shown in the GUI of the editor.

I would prefer the first solution, but could be it is a problem of the internal
HSQLDB, which couldn't be changed.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 108058] After renaming Primary Key AutoValue feature fails

2017-05-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108058

--- Comment #2 from Howard Johnson  ---
Alex, 

First let me say that I very much appreciate your looking into this and all of
the other work you've done on LO!

But just to be clear, I did not submit this report or the others to find
workarounds, but rather to provide the basis to start to fix these issues in
the first place.  I want Base to work better, not to have to send users looking
for obscure answers related to very introductory and simple issues like
renaming a field.

All in all, it's pretty clear to me that we're in a pretty bad way in terms of
overall LO Base maintenance.

Other than that I'm not sure what to think.  I've been told by a couple of guys
that the LO code base is relatively very big, and complex.  So it is.

What in your opinion is needed to improve the overall efforts to address some
of these fundamental Base issues?


(FYI: I have again tried to build LO just so I could take a look at it.  But I
again ran into the same problem that I ran into when I first tried this,
documented here: 
https://ask.libreoffice.org/en/question/96902/building-lo-w-mariadb-installed-fails/)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 108058] After renaming Primary Key AutoValue feature fails

2017-05-24 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108058

--- Comment #1 from Alex Thurgood  ---
(In reply to Howard Johnson from comment #0)


> The only way I have found to fix this is to delete the table and start over. 

No, that shouldn't be necessary, just delete the Primary Key from the table in
the UI, then use an ALTER TABLE statement via the Tools > SQL menu entry :


http://ooo-forums.apache.org/en/forum/viewtopic.php?f=61=64482#p286456




> 
> This is a very basic malfunction that a new Base user will likely run into. 

This is a well documented known limitation, as the above link shows. If you
still have a problem with the auto increment function not working once you have
deleted the primary key from the table, then issued the ALTER TABLE command,
there might be reason to file a bug report for that.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs