Firebird 2.1 在某些数据库表中存储大量行是否有效？
我的应用程序不断收到一个需要存储的非常小的事件，我在想哪种是处理它的最佳方法。该事件的表将如下所示：
EVENT
id
timestamp
some_data (integer)
fk_to_some_holder_table
如果我继续将每个事件存储为一行，对于使用某种 blob 压缩/处理的实现是否会存在一些缺点？还是我在这里太过分了？
我正在使用火鸟 2.1。如果需要，我可以升级到 Firebird 2.5。
提前致谢。
My application keeps receiving a really small event that it needs to store and I was thinking which is the best way to handle it. The table for this event would be something like this:
EVENT
id
timestamp
some_data (integer)
fk_to_some_holder_table
If I keep storing each event as a row, will there be some disadvantage against an implementation with some kind of blob compression/treatment? Or am I going too far here?
I'm using Firebird 2.1. If needed, I could upgrade to Firebird 2.5.
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我确信您最好使用“传统的基于行的记录”：
根据“Firebird的技术限制是什么？”一文，一张表的最大大小为32TB或16G行。
我认为在这种特定情况下 2.1 和 2.5 之间没有任何区别，但由于其他/一般改进，我会使用 2.5。
I'm sure you're better off with "traditional row based record":
According to the "What are the technical limits of Firebird?" article maximum size of one table is 32TB or 16G rows.
I don't think there is any difference between 2.1 and 2.5 in this specific case, but I'd use 2.5 because of other/general improvements.
存储为行比 blob 更有意义，出于已经提到的原因
，我现在坚持使用 2.1，2.5 有太多我不喜欢的错误
storing as a row makes much better sense than blobs, for the reasons already mentioned
I'd stick with 2.1 for now, 2.5 has too many bugs for my liking