Hi guys Well thats a update at a field with a where with full primary key fields Where with (Fields)=(consts) or field=const and field=const ... Work the same way with same time ---- Yes thats a bigint field (with int i got same problem) the first partition is used for negative values And others partitions to positive values I'm running update only at negative values all others rows (partitions) with positive value only have insert, no updates and no delete I'm using the primary key at where clausule in other words i'm using a unique key or a unique index. I'm updating a field without indexes (a field not indexed) I don't know why the mariadb stop 5 seconds or more, since it's a partition with less than 1000 rows and no index field was changed Any ideas? Em terça-feira, 17 de junho de 2014, James Briggs <james.briggs@yahoo.com> escreveu:
Hi Roberto.
1) nf is a bigint, so why are you inserting a string value ('-18')? 2) is there some reason you aren't using indexes? 3) after you resolve 1 and 2, do repair table.
Thanks, James.
-------------------------------------------- On Tue, 6/17/14, Roberto Spadim <roberto@spadim.com.br <javascript:;>> wrote:
Subject: [Maria-developers] problem with update and myisam To: "maria-developers@lists.launchpad.net <javascript:;>" < maria-developers@lists.launchpad.net <javascript:;>> Date: Tuesday, June 17, 2014, 1:31 PM
hi guys, could anyone help me with https://mariadb.atlassian.net/browse/MDEV-6355 thanks
-- Roberto Spadim
-----Inline Attachment Follows-----
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net <javascript:;> Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
-- Roberto Spadim SPAEmpresarial Eng. Automação e Controle