blocks|key|127930|text|为什么不像保存属性一样将它们保存在表中。那是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|127931|%7C+id%7C+name+++++++%7C+value++++++++%7C
%2B---%2B------------%2B--------------%2B
%7C+1+%7C+array_key++%7C+array_value++%7C
%7C+2+%7C+array_key2+%7C+array_value2+%7C|code-block|syntax|javascript|127932|如果想要数组的多个实例，可以始终添加一个额外的键来跟踪实例：|127933|%7C+id%7C+name+++++++%7C+value++++++++%7C+instance_key+%7C
%2B---%2B------------%2B--------------%2B--------------%2B
%7C+1+%7C+array_key++%7C+array_value++%7C+1++++++++++++%7C
%7C+2+%7C+array_key2+%7C+array_value2+%7C+1++++++++++++%7C
%7C+3+%7C+array_key++%7C+array_value++%7C+2++++++++++++%7C
%7C+4+%7C+array_key2+%7C+array_value2+%7C+2++++++++++++%7C|127934|使用这类解决方案的方法的问题是，数据往往更难读，并且如果一个对象有几个属性，就会有很多额外的连接。|127935|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Why not save them like like properties in a table. that is

<pre><code>| id| name | value |
+---+------------+--------------+
| 1 | array_key | array_value |
| 2 | array_key2 | array_value2 |
</code></pre>

If one wants multiple instances of the array, one could always add an extra key for keeping track of the instances:

<pre><code>| id| name | value | instance_key |
+---+------------+--------------+--------------+
| 1 | array_key | array_value | 1 |
| 2 | array_key2 | array_value2 | 1 |
| 3 | array_key | array_value | 2 |
| 4 | array_key2 | array_value2 | 2 |
</code></pre>

Problem with the approach of using this kinds of solutions is that the data tend to be more less human-readable and there be alot of extra joins if you have several properties on an object.

blocks|key|1131234|text|你有几张唱片？上百个？几千人？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1131235|如果您的记录数低于500，那么我认为您根本不应该选择数据库。您可以将其存储在XML文件中。这是NoSQL+:)的时代。|offset|length|1131236|并不是说我支持这项运动，但对于您的需求来说，数据库似乎过于雄心勃勃。|1131237|entityMap|0|LINK|mutability|MUTABLE|url|http://www.computerworld.com/s/article/9135086/No_to_SQL_Anti_database_movement_gains_steam_^0|0|1B|5|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

How many records do you have? Hundreds? Thousands? 

If your record count is below 500 then I don't think you should pick up a database at all. You could store that in a XML file. These are the times of <a href="http://www.computerworld.com/s/article/9135086/No_to_SQL_Anti_database_movement_gains_steam_" rel="nofollow noreferrer">NoSQL</a> :).

Not that I support the movement, but a database seems like overambition for your requirement.

blocks|key|127880|text|正如您所提到的，您应该有一个键列和一个值列，并插入记录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|127881|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You'd pretty much have a column for the key, and a column for the value, and insert the records, as you mentioned.

blocks|key|1131135|text|如果您存储的数据不用于搜索数据库，并且只在应用程序代码中更新，那么我倾向于将其存储为blob。如果您可能要更新它的一部分，并且不需要读取完整的数据集来进行有意义的更新，那么可以使用包含id、user_id、键、值等列的单独的表。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1131136|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If the data you are storing isn't used for searching the database, and is only updated in application code, then I would lean towards just storing it as a blob. If you are likely to update portions of it and don't need to read the full set of data to make meaningful updates, then a separate table with columns like id, user_id, key, value would be the way to go.

blocks|key|127903|text|写出一个for循环来创建您的INSERT语句，然后执行查询，将数组保存到一个包含键和值列的表中。要重新创建数组，请从表中检索它，然后使用另一个for循环将值重新插入到数组中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|127904|我在这种设置中看到的唯一问题是，如果您计划拥有数组的多个实例，并且必须保存所有这些实例，因为数据库表只能表示数组的一个实例。|127905|如果计划拥有多个实例，最好的方法是序列化并存储在blob或文本列中。|127906|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Write out a for-loop to create you INSERT statement, then just execute the query to save the array into a table with key and value columns. To recreate the array, retrieve it from the table and use another for loop to reinsert the values into an array.

Only problem I can see in this kind of setup is that if you plan to have multiple instances of the array, and all these instances have to be saved, as the database table can only represent one instance of the array.

If planning to have multiple instances, best way would be to serialize and store in a blob or TEXT column.

blocks|key|1430249|text|我以前使用过的json_encode()和json_decode()函数来做这类事情：http://uk.php.net/json_encode|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1430250|您需要做的就是在数据库中有一个文本字段，并将JSON编码的数组插入其中。如果不需要搜索存储的数据，这是一种非常有效的存储数据的方法，因为您可以根据需要轻松快速地将JSON字符串转换回PHP数组并输出。|1430251|您还可以查看YAML，尽管PHP似乎还没有一组用于解析YAML的内置函数，因此需要一个外部类：http://railsforphp.com/2008/01/08/php-meet-yaml/+http://railsforphp.com/2008/01/08/php-meet-yaml/。|1430252|entityMap|0|LINK|mutability|MUTABLE|url|http://uk.php.net/json_encode|1|http://railsforphp.com/2008/01/08/php-meet-yaml/^0|6|E|L|D|17|T|0|0|0|1B|2P|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|J|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]|R|$5|M|N|O|E|$P|S]]]]

I've used JSON for this sort of thing in the past using PHP5's json_encode() and json_decode() functions: <a href="http://uk.php.net/json_encode" rel="nofollow noreferrer">http://uk.php.net/json_encode</a>

All you need to do is have a text field in your database and insert the JSON encoded array into it. If there isn't a need to search the data you're storing it's quite an efficient way of storing data because you can easily and quickly convert the JSON string back into a PHP array and output as required.

You could also look into YAML, although PHP doesn't yet appear to have a built in set of functions for parsing YAML, so an external class is required: <a href="http://railsforphp.com/2008/01/08/php-meet-yaml/" rel="nofollow noreferrer">http://railsforphp.com/2008/01/08/php-meet-yaml/ http://railsforphp.com/2008/01/08/php-meet-yaml/</a>

blocks|key|1131314|text|最好也是最简单的方法是使用serialize。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1131315|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Your best and simplest way is to use serialize.

I have a really long list of itinerary items with integer values. I was thinking about creating a database with each of these items with like fifty columns but that seemed a bit long-winded, and the itinerary may change. Is there a better way to store these name => value pairs in a database? serializing seems a bit crude, I was thinking about just creating an itinerary_items db with name, value columns and sticking the data in there. What is the best solution?

Storing a large array in a database

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个很长的带有整数值的行程项目列表。我正在考虑创建一个数据库，其中每个项目都有大约50列，但这似乎有点冗长，而且行程可能会改变。有没有更好的方法在数据库中存储这些名称=>值对？序列化看起来有点粗糙，我在考虑只创建一个包含名称、值列的itinerary_items数据库，并将数据保存在其中。最佳解决方案是什么？

问在数据库中存储大型数组
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在数据库中存储大型数组EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在数据库中存储大型数组
EN