维护/更新mysql中的记录顺序
我在 mySql 中有一个记录表。 我需要按照用户指定的方式维护它们的订单。 所以我添加了一个“位置”列。
当我移动特定记录时更新所有记录的 SQL 语句是什么? 我有这样的想法:
UPDATE items SET position = '2' WHERE id ='4';
UPDATE items SET position = position+1 WHERE position >= '2' AND id != '4';
但是如果记录向下移动,则大于将小于。 有什么窍门呢? 谢谢!
I have a table of records in mySql. I need to maintain an order for them as specified by the user. So I've added a 'position' column.
What would be the SQL statement to update all the records when I move a specific record? I've got something like:
UPDATE items SET position = '2' WHERE id ='4';
UPDATE items SET position = position+1 WHERE position >= '2' AND id != '4';
But the greater than is going to be a less than if the record has moved down. What's the trick? Thanks!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(7)
像这样的事情会做吗?
我测试了几次,似乎有效。
Would something like this do it?
I tested it a couple of times and it seems to work.
对于例如具有由用户维护的行号的销售订单执行此类操作,我发现最好在 BL 或 UI 中的数组中处理它。 通常他们会想要调整几条记录,有时想说“算了”。 因此,最简单的方法可能是等到他们点击“确定”按钮(或类似的按钮),然后用当前的顺序将它们全部写回。
您最终也可能会处理删除,这是您可以用相同方式处理的另一个问题。
Doing this sort of thing for e.g. sales orders with line numbers maintained by the user, I've found it best to handle it in an array in the BL or UI. Usually they will want to adjust several records, and sometimes want to say "forget it". So the easiest might be to just wait until they hit the "OK" button (or your equivalent) and then write them all back with current ordering.
You may end up dealing with deletions, too, which is another problem you can handle the same way.
这是我对此的看法:我的 row_index 列的数字步长为 10(例如:0、10、20,等等)。 当用户更新其中一行时,您需要知道它是上升还是下降。 如果必须将第 2 行移至第 4 行(向下,所需 row_index = 30),请将 row_index 设置为 35; 否则(如果向上)将其设置为 25。设置此值:
现在您的顺序正确,但 row_indexes 混乱。 要解决此问题,请执行以下两个查询:
这将更新所有行(或使用 where 语句选择的行)并设置无间隙的 row_index 列(0、10、20、30 等)。 当然,这种方式会增加写入操作的负载,但我认为这是在读取操作期间获取顺序的最快方法。 如果删除一行,您只需重新运行固定订单查询即可。
This is my take on this: my row_index column has number with a step of 10 (eg.: 0, 10, 20, ecc.). When a user updates one of the row you need to know if it's going up or down. If you have to move the 2nd row to the 4th (going down, desired row_index = 30), you set the row_index to 35; otherwise (if going up) set it to 25. Set this value:
Now you have the correct order, but the row_indexes are messed up. To fix this, execute this two queries:
This is going to update all your rows (or the one you select with the where statement) and set the row_index column without gaps (0, 10, 20, 30, ecc.). Surely this way adds load on the write operations, but I think it's the fastest way to get the order during read operations. If you delete a row you can just re run the fixing order queries.
我建议至少在项目之间使用较大的增量(例如 10000)。 然后只需执行订单即可。 如果您需要将 11000 移动到 9000 到 10000 之间,则只需将其设置为 9500 即可。
这并不能消除重新排序的问题,但可以大大减少它。 在某些时候,您最好删除所有行,然后以正确的顺序读取它们。 恕我直言,像您这样进行更新太容易出错。
I would suggest, at a minimum, using large increments (say 10000) between items. Then just doing an order by. If you need to move 11000 to between 9000 and 10000 then just set it to 9500 and done.
This doesn't eliminate the problem of reordering but it greatly reduces it. At some point you're better off deleting all the rows then readding them with the correct order. Doing updates like you're doing is just too error prone imho.
您可能会考虑使用链表类型的方法,带有指向列表中下一个项目(也可能是前一个项目)的键,那么您只需更新一些记录,而不是全部记录。
You might consider using a linked list type of approach, with a key to the next, and maybe the previous item in the list, then you only have to update a few records, instead of all of them.
有趣的! 好吧,所以没有简单的答案。 我以为我只是错过了一些东西。 我想过维护一个外部阵列。 这听起来是最好的主意。
Interesting! Okay, so there is no easy answer. I thought I was just missing something. I'd thought about maintaining an external array. That sounds like the best idea.
也许是这样的?
Maybe something like this?