https://bugs.documentfoundation.org/show_bug.cgi?id=90780

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |UNCONFIRMED
     Ever confirmed|1                           |0

--- Comment #3 from [email protected] ---
(In reply to Alex Thurgood from comment #1)
> @ronny :
> In your blog post, you mention that you only tested 3.6.x, 4.0.x and
> apparently 4.1. Those versions are very old, in fact obsolete with regard to
> currently supported production versions of LibreOffice that are available on
> the download page.
> 
> It might well be that the problems with primary key retrieval you mention
> have been resolved in these later versions.
> 
> Additionally, if I have understood correctly, all of your tests were carried
> out by dragging the query resultset into a Calc sheet - can you confirm this
> ?
> 
> I have a remote non-SSH connection to a local LAN mysql instance (not
> MariaDB) to which I connect from a Mac, and although I don't have as many
> records, I don't see a noticeable performance hit when scrolling through a
> resultset of all records of a table containg 75 columns by 4400 tuples. Note
> that each tuple is identified by an AUTO_INCREMENT NOT NULL PRIMARY KEY
> definition, guaranteeing uniqueness. I also use the native mysql connector.
> 
> I will set this to NEEDINFO to await your tests with the latest production
> releases of LO. Please set back to UNCONFIRMED afterwards.
> 
> Adding Lionel, Julien to CC

Thx for reply! The blog post was not published by me, just found it on the web.
As filled in the bug form, I tested on 4.4.2.2 (latest stable).

I tested the issue in data grid controls in form and just by looking tables in
the table view, i. e., simple select queries (I’m using German localization,
hopefully the terms a right).

I have created a simple table (MySQL 5.5):

CREATE TABLE `artists` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(200) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=14 DEFAULT CHARSET=utf8;


As you can see, I created a AUTO_INCREMENT NOT NULL PRIMARY KEY. The funny
thing is, changing `id` to UNIQUE only does not raise the issue. Btw. I filled
the table with 200 rows only.

Do you think it could be helpful to test LO Base on a Linux on a virtual box?

Best regards, Ronny

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to