blocks|key|1256066|text|任何问题“我应该使用某个工具吗？”归根结底就是问你到底想做什么。您应该问自己--“我想为这些数据编写自己的存储空间吗？”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1256067|大多数基于web的应用程序都是针对数据库编写的，因为大多数数据库都支持许多“免费”功能--您可以有多个web服务器。您可以使用标准工具来编辑、验证和备份您的数据。您可以拥有一个强大的事务存储解决方案。|1256068|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Any question "Should I use a certain tool?" comes down to asking exactly what you want to do. You should ask yourself - "Do I want to write my own storage for this data?"

Most web based applications are written against a database because most databases support many "free" features - you can have multiple webservers. You can use standard tools to edit, verify and backup your data. You can have a robust storage solution with transactions.

blocks|key|5104499|text|数据库在处理图像数据本身方面不会有太多帮助，但是管理一组图像的任何东西都将拥有关于您要处理的图像的元数据。根据元数据和您想要对它做什么，数据库确实可以对此非常有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5104500|仅仅因为数据库对图像数据没有太多帮助，并不意味着您不能将图像存储在数据库中。您可以将它们存储在SQL数据库的BLOB列中。|5104501|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The database won't help you much in dealing with the image data itself, but anything that manages a bunch of images is going to have meta-data about the images that you'll be dealing with. Depending on the meta-data and what you want to do with it, a database can be quite helpful indeed with that.

And just because the database doesn't help you much with the image data, that doesn't mean you can't store the images in the database. You would store them in a BLOB column of a SQL database.

blocks|key|1320232|text|如果数据量很小，或者安装在许多客户端计算机上，您可能不想要数据库的开销。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1320233|它是否打算安装在多个用户的机器上？增加确保您可以在客户端安装的应用程序上运行您选择的任何数据库引擎的开销并不是最优的。由于数据量很小，我认为XML在这里就足够了。您可以对图像进行Base64编码，并将其存储为CDATA。|1320234|应用程序将在服务器上运行吗？如果您有并发用户，那么数据库就有处理这些场景(事务)的概念，这会很有帮助。并且扫描的图像数据将适合于斑点。|1320235|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|$]]

If the amount of data is small, or installed on many client machines, you might not want the overhead of a database.

Is it intended to be installed on many users machines? Adding the overhead of ensuring you can run whatever database engine you choose on a client installed app is not optimal. Since the amount of data is small, I think XML would be adequate here. You could Base64 encode the images and store them as CDATA.

Will the application be run on a server? If you have concurrent users, then databases have concepts for handling these scenarios (transactions), and that can be helpful. And the scanned image data would be appropriate for a BLOB.

blocks|key|5104674|text|您不应该将图像存储在数据库中，因为这是一般的共识here。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5104675|在存储图像方面，文件系统要比数据库好得多。|5104676|您应该使用数据库来存储有关这些图像的元信息，例如标题、描述等，并且只存储图像的URL或路径。|5104677|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/3748/storing-images-in-db-yea-or-nay^0|O|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

You shouldn't store images in the database, as is the general consensus <a href="https://stackoverflow.com/questions/3748/storing-images-in-db-yea-or-nay">here</a>.

The file system is just much better at storing images than your database is.

You should use a database to store meta information about those images, such as a title, description, etc, and just store a URL or path to the images.

blocks|key|5104720|text|当涉及到在数据库中存储图像时，我尽量避免它。在你的情况下，从我所能收集到的你的问题中，有可能出现相当大的图像，所以我可能会强烈反对。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5104721|如果这是一个web应用程序，我会使用数据库来使用关键字和其他参数对图像进行快速搜索和索引。然后，如果可能的话，让一列指向图像在文件系统中的位置，并使用某种文件夹结构来帮助进一步减少图像加载时间。|5104722|如果由于目录可用(网络共享)而需要更高的安全性，而应用程序是本地的，那么您可能应该咬紧牙关，将图像存储在数据库中。|5104723|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|$]]

When it comes to storing images in a database I try to avoid it. In your case from what I can gather of your question there is a possibilty for a subsantial number of fairly large images, so I would probably strong oppose it.

If this is a web application I would use a database for quick searching and indexing of images using keywords and other parameters. Then have a column pointing to the location of the image in a filesystem if possible with some kind of folder structure to help further decrease the image load time.

If you need greater security due to the directory being available (network share) and the application is local then you should probably bite the bullet and store the images in the database.

blocks|key|5104382|text|我的直觉反应是“何乐而不为？”数据库将提供一个存储信息的框架，所有的输入/输出/优化功能都以文档格式提供。可以使用服务器端解决方案，也可以使用本地数据库，如SQLite或SQL+Server的本地版本。无论哪种方式，您都有一个健壮的、有文档记录的数据管理框架。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5104383|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|$]]

My gut reaction is "why not?" A database is going to provide a framework for storing information, with all of the input/output/optimization functions provided in a documented format. You can go with a server-side solution, or a local database such as SQLite or the local version of SQL Server. Either way you have a robust, documented data management framework.

blocks|key|3636168|text|关于在数据库中存储图像，This+post应该会为您提供所需的大多数意见。你的意思也是‘我应该使用数据库来存储其他信息吗？’或者你只是在问图像的问题？|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3636169|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/3748/storing-images-in-db-yea-or-nay^0|C|9|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="https://stackoverflow.com/questions/3748/storing-images-in-db-yea-or-nay">This post</a> should give you most of the opinions you need about storing images in the database. Do you also mean 'should I use a database for the other information?' or are you just asking about the images?

blocks|key|5104467|text|我们的CMS存储了我们处理的所有支票图像。它使用元数据数据库，并让文件系统处理扫描的图像。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5104468|像SQLite这样的简单数据库听起来很合适--它可以让您以一致的、事务性的方式存储文件元数据。然后将每个映像的路径存储在数据库中，并让文件系统做它最擅长的事情-管理文件。|5104469|SQL+Server2008为数据库中的文件构建了一种新的数据类型，但在此之前，BLOB是在数据库中存储文件的方式。在小规模的情况下，这也是可行的。|5104470|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|$]]

Our CMS stores all of the check images we process. It uses a database for metadata and lets the file system handle the scanned images. 

A simple database like SQLite sounds appropriate - it will let you store file metadata in a consistent, transactional way. Then store the path to each image in the database and let the file system do what it does best - manage files.

SQL Server 2008 has a new data type built for in-database files, but before that BLOB was the way to store files inside the database. On a small scale that would work too.

blocks|key|1320254|text|数据库旨在管理大量数据，并且应该让您快速访问以读取和写入数据，而不管数据的大小。简单地说，它们管理您不想处理的数据规模。如果您只有几个用户(数百个？)，那么您可以同样轻松地管理磁盘上的数据(比如XML?)并将数据保存在内存中。图像显然不应该放到数据库中，所以问题是有多少数据，或者您为多少用户维护这个数据库实例？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1320255|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|$]]

A database is meant to manage large volumes of data, and are supposed to give you fast access to read and write that data in spite of the size. Put simply, they manage scale for data - scale that you don't want to deal with. If you have only a few users (hundreds?), you could just as easily manage the data on disk (say XML?) and keep the data in memory. The images should clearly not go in to the database so the question is how much data, or for how many users are you maintaining this database instance?

blocks|key|1262221|text|如果你想有一种结构化的方式来存储和检索信息，那么数据库无疑是最好的选择。它使您的应用程序更加灵活和强大，并使您能够专注于实际的应用程序，而不是像尝试编写自己的存储系统那样的附带内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1262222|对于单独的应用程序，SQLite是很棒的。它以文件的形式恰好适合应用程序；不需要整个DRBMS主宰。|offset|length|1262223|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sqlite.org/^0|0|A|6|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

If you want to have a structured way to store and retrieve information, a database is most definitely the way to go. It makes your application flexible and more powerful, and lets you focus on the actual application rather than incidentals like trying to write your own storage system. 

For individual applications, <a href="http://www.sqlite.org/" rel="nofollow noreferrer" title="SQLite">SQLite</a> is great. It fits right in an app as a file; no need for a whole DRBMS juggernaut.

blocks|key|5104634|text|这其中有很多因素。但是，作为一个数据库专家，我会在拥有一个数据库方面犯错误。当事情发生变化时，它只会让生活变得更容易。一切都会改变的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5104635|根据图像的不同，您可能会将它们存储在文件系统中，或者实际上是blob并将它们放入数据库(并非所有DBMS都支持)。如果文件非常小，那么我会对它们进行blob。如果它们很大，那么我会将它们保存在文件系统中，然后自己管理它们。|5104636|有如此之多的免费或廉价的数据库管理系统，以至于没有任何借口不使用它。我是一个SQL+Server的家伙，但如果你的应用程序这么简单，那么mysql的免费版本应该可以完成这项工作。事实上，它里面有一些很酷的东西。|5104637|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|$]]

There are a lot of factors to this. But, being a database weenie, I would err on the side of having a database. It just makes life easier when things changes. and things will change.

Depending on the images, you might store them on the file system or actually blob them and put them in the database (Not supported in all DBMS's). If the files are very small, then I would blob them. If they are big, then I would keep them on he file system and manage them yourself.

There are so many free or cheap DBMS's out there that there really is no excuse not to use one. I'm a SQL Server guy, but f your application is that simple, then the free version of mysql should do the job. In fact, it has some pretty cool stuff in there.

I have been hired to help write an application that manages certain information for the end user. It is intended to manage a few megabytes of information, but also manage scanned images in full resolution. Should this project use a database, and why or why not?

How important is a database in managing information?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我受雇帮助编写一个为最终用户管理某些信息的应用程序。它的目的是管理几兆字节的信息，但也管理全分辨率的扫描图像。这个项目应该使用数据库吗?为什么不使用数据库？

问数据库在管理信息方面有多重要？
EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问数据库在管理信息方面有多重要？EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问数据库在管理信息方面有多重要？
EN