MySQL存储过程返回不同的结果

Question

我有一个查询，应该搜索表中的行，找到任何包含搜索词（例如'狗％'）的行，然后返回相关父代的id（从不同的表）。所以，我通过父母ID对结果进行分组，然后对其进行重新排序，最后，通过限制/偏移量来获得10个uniqe ID列表。查询是在存储过程中，我从PHP调用它。

问题是，我经常得到不同的结果。即使IN参数相同，但数据库中没有任何更改，我可以得到非常不同的结果每个请求 - ID不一样，有顺序的差异，我得到重复ID在两个请求...

这是程序：

CREATE DEFINER=`root`@`localhost` PROCEDURE `FIND_VOCABULARY_ID_BY_MEANING`(IN `in_searched_value` varchar(50) 
, IN `in_offset` INT) 
    LANGUAGE SQL 
    NOT DETERMINISTIC 
    CONTAINS SQL 
    SQL SECURITY DEFINER 
    COMMENT '' 
BEGIN 
     insert into test values (in_searched_value,in_offset); 

     SELECT 
     v.id 
     FROM vocabulary AS v 
     LEFT JOIN vocabulary_sense AS vs ON vs.vocabulary_id = v.id 
     LEFT JOIN vocabulary_sense_gloss_eng AS vsg ON vsg.sense_id = vs.id 
     WHERE vsg.gloss LIKE CONCAT(in_searched_value,'%') 
     GROUP BY v.id 
     ORDER BY v.calculated_prio DESC  
     LIMIT 10 OFFSET in_offset; 
END 

我怎么称呼它：

$stmt = $this->pdo->prepare("CALL $procedureToCall('$searchedTerm', $offset)"); 

在PHP中，我记录的值（请求，那么它的结果）日志文件。这里有两种不同的方法，在每个有五个请求：

[2016-10-11 13:35:19] CALL FIND_VOCABULARY_ID_BY_MEANING('vulgar', 0) 
[2016-10-11 13:35:19] 17141,16446,38334,58166,17121,45822,35328,37553,41185,45832 
[2016-10-11 13:35:22] CALL FIND_VOCABULARY_ID_BY_MEANING('vulgar', 10) 
[2016-10-11 13:35:22] 46659,51149,53639,55276,56388,95,63900,71780,73935,17134 
[2016-10-11 13:35:25] CALL FIND_VOCABULARY_ID_BY_MEANING('vulgar', 20) 
[2016-10-11 13:35:25] 83260,97433,17176,103416,111512,135069,147790,38335,159709,38338 
[2016-10-11 13:35:27] CALL FIND_VOCABULARY_ID_BY_MEANING('vulgar', 30) 
[2016-10-11 13:35:27] 162898,38340,163783,38359,165067,38360,171044,38364,38378,38380 
[2016-10-11 13:35:31] CALL FIND_VOCABULARY_ID_BY_MEANING('vulgar', 40) 
[2016-10-11 13:35:31] 38384,41163,41211,45832,45833,45837 
[2016-10-11 13:35:33] CALL FIND_VOCABULARY_ID_BY_MEANING('vulgar', 50) 

[2016-10-11 13:50:38] CALL FIND_VOCABULARY_ID_BY_MEANING('vulgar', 0) 
[2016-10-11 13:50:38] 17141,16446,38334,58166,17121,45822,35328,37553,41185,56388 
[2016-10-11 13:50:41] CALL FIND_VOCABULARY_ID_BY_MEANING('vulgar', 10) 
[2016-10-11 13:50:41] 95,63900,71780,73935,17134,83260,97433,17176,103416,111512 
[2016-10-11 13:50:45] CALL FIND_VOCABULARY_ID_BY_MEANING('vulgar', 20) 
[2016-10-11 13:50:45] 135069,147790,38335,159709,38338,162898,38340,163783,38359,165067 
[2016-10-11 13:50:48] CALL FIND_VOCABULARY_ID_BY_MEANING('vulgar', 30) 
[2016-10-11 13:50:48] 38360,171044,38364,38378,38380,38384,41163,41211,45832,45833 
[2016-10-11 13:50:50] CALL FIND_VOCABULARY_ID_BY_MEANING('vulgar', 40) 
[2016-10-11 13:50:50] 45837,45841,46659,51149,53639,55276 
[2016-10-11 13:50:53] CALL FIND_VOCABULARY_ID_BY_MEANING('vulgar', 50) 

正如你可以看到，45832 ID被发送给了我两次在第一种方法（偏移0和40）。在第二种方法中，它存在一次，但在偏移30 ...

我也记录输入参数 - 偏移量和searledTerm - 在Mysql中 - 也有正确的，与上面生成的PHP日志一致。那么，为什么我有这些diffenreces？我在这里做错了什么？

编辑

我发现，调用过程直接从MySQL客户端（不是PHP）给我consitent结果 - 但话又说回来，当我打电话只是普通的查询：

SELECT 
    v.id 
    FROM vocabulary AS v 
    LEFT JOIN vocabulary_sense AS vs ON vs.vocabulary_id = v.id 
    LEFT JOIN vocabulary_sense_gloss_eng AS vsg ON vsg.sense_id = vs.id 
    WHERE vsg.gloss LIKE CONCAT('vulgar','%') 
    GROUP BY v.id 
    ORDER BY v.calculated_prio DESC  
    LIMIT 10 OFFSET 0; 

结果也不同（仍然consitent，我得到了相同的结果，而这些结果从内部程序查询不同）...

EDIT 2

^h ere是查询中使用的表格结构：

CREATE TABLE `vocabulary` (
    `id` MEDIUMINT(8) UNSIGNED NOT NULL AUTO_INCREMENT, 
    `entry_sequence` MEDIUMINT(8) UNSIGNED NOT NULL, 
    `jlpt_level` TINYINT(4) NULL DEFAULT NULL, 
    `calculated_prio` MEDIUMINT(9) NOT NULL DEFAULT '0', 
    PRIMARY KEY (`id`), 
    INDEX `idx_vocabulary_calculated_prio` (`calculated_prio`) 
) 
COLLATE='utf8_general_ci' 
ENGINE=InnoDB 
AUTO_INCREMENT=174912 
; 


CREATE TABLE `vocabulary_sense` (
    `id` MEDIUMINT(8) UNSIGNED NOT NULL AUTO_INCREMENT, 
    `vocabulary_id` MEDIUMINT(8) UNSIGNED NOT NULL, 
    PRIMARY KEY (`id`), 
    INDEX `fk_vocabulary_sense_vocabulary_id` (`vocabulary_id`), 
    CONSTRAINT `fk_vocabulary_sense_vocabulary_id` FOREIGN KEY (`vocabulary_id`) REFERENCES `vocabulary` (`id`) 
) 
COLLATE='utf8_general_ci' 
ENGINE=InnoDB 
AUTO_INCREMENT=195529 
; 


CREATE TABLE `vocabulary_sense_gloss_eng` (
    `id` MEDIUMINT(8) UNSIGNED NOT NULL AUTO_INCREMENT, 
    `sense_id` MEDIUMINT(8) UNSIGNED NOT NULL, 
    `gloss` TEXT NOT NULL, 
    PRIMARY KEY (`id`), 
    INDEX `vocabulary_sense_gloss_vocabulary_sense_id` (`sense_id`), 
    INDEX `vocabulary_sense_gloss_gloss` (`gloss`(255)), 
    CONSTRAINT `vocabulary_sense_gloss_eng` FOREIGN KEY (`sense_id`) REFERENCES `vocabulary_sense` (`id`) 
) 
COLLATE='utf8_general_ci' 
ENGINE=InnoDB 
ROW_FORMAT=COMPACT 
AUTO_INCREMENT=317857 
; 

词汇是主要条目。 vocabulary_sense（一对多）指向它。而且vocabulary_sense_gloss_eng（又是一对多）正指向vocabulary_sense。

“calculated_prio”只是一个静态INT值。

Answer 1

哦该死，我太愚蠢:)

问题是与排序，calculated_prio不得不为第一九行正值只，并为他们的休息，这只是0，所以只有第一九行均特定的顺序，其他一切都是随机的。