dongliao3742 2011-08-02 06:56
浏览 54
已采纳

将`INT`主键打包成一个`LONG`

Is it efficient to "pack" two INT primary keys (a composite key) into a single BIGINT primary key? Can it be done automatically within mySQL or does it need to be done in the client (PHP, C++)?

I'm creating a directional graph connecting user IDs to one another (e.g. for a friend-finder) in mySQL.

MySQL supports 8-byte BIGINTs and 4-byte INTs, so the packer might look something like:

id_edge = ((BIGINT)id_from)*pow(2,31) + ((BIGINT)id_to)

How do the big boys (FB, LI) do it? Is it easier or better to have three "independent" fields:

CREATE  TABLE `things`.`connections` (
`id_edge` BIGINT NOT NULL AUTO_INCREMENT COMMENT 'Need a single pk for gii
' ,
`id_from` INT NOT NULL ,
`id_to` INT NOT NULL ,
....
  • 写回答

2条回答 默认 最新

  • dongpo1216 2011-08-02 07:01
    关注

    No. You shouldn't be seeking to micro-optimise the storage. Each column should store 1 piece of data - no more and no less.

    If you implemented the packing you propose, you'd make indexing impossible - a full table scan would be required to find e.g. all rows with id_to equal to 19.


    You can also read Chapter 13 of the MySQL manual, which discusses the various storage engines and how they actually store table data.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论
查看更多回答(1条)

报告相同问题?

悬赏问题

  • ¥50 如何增强飞上天的树莓派的热点信号强度,以使得笔记本可以在地面实现远程桌面连接
  • ¥15 MCNP里如何定义多个源?
  • ¥20 双层网络上信息-疾病传播
  • ¥50 paddlepaddle pinn
  • ¥20 idea运行测试代码报错问题
  • ¥15 网络监控:网络故障告警通知
  • ¥15 django项目运行报编码错误
  • ¥15 STM32驱动继电器
  • ¥15 Windows server update services
  • ¥15 关于#c语言#的问题:我现在在做一个墨水屏设计,2.9英寸的小屏怎么换4.2英寸大屏