本文介绍了关系数据到非关系数据的合理导出的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

由于各种原因,我们有不同的产品依赖关系数据库,基本上是操作的事务性质(原子性、一致性等).这不会很快改变.

We have different products that rely on relational databases for various reasons, basically the transactional nature of the operations (atomicity, consistency, etc.). This is not going to change any time soon.

鉴于这种情况,是否有任何可能的理由将数据导出到 NoSQL 解决方案?可能是数据仓库、分析等.

Given this scenario, are there any possible justifications to export the data to a NoSQL solution? Maybe Datawarehousing, Analytics, etc.

欢迎提出任何意见.

推荐答案

数据"只是一个没有数据结构的模糊概括.关系"意味着数据结构是具有通用查询的关系/表.(不是自动交错执行语义原子并发事务,这恰好成为可行给定的关系集合运算符.)需要 对于专门的数据结构或查询,建议增强一个关系系统接口或实现.NoSQL"是各种具有特殊情况抽象和/或实现的此类系统的统称.但它们不需要在界面上是非关系的.它们只需要不是当前的关系"DBMS 所提供的.鉴于它们存在,人们可以在需要时合理地向它们导出(或从它们导入).

"Data" is just a vague generality without a data structure. "Relational" means the data structure is relations/tables with generic queries. (Not automatically interleaved execution of semantically atomic concurrent transactions, which just happens to become feasible given relational set-at-a-time operators.) Need for specialized data structures or queries suggests augmenting a relational system interface or implementation. "NoSQL" is a catch-all for all sorts of such systems with special-case abstractions and/or implementations. But they don't need to be non-relational in interface. They just need to be not what current "relational" DBMSs provide. Given that they exist, one can reasonably export to (or import from) them when needed.

不幸的是,关系模型通常不被理解(包括关系"DBMS),因此这些系统拒绝他们可以简单地扩展的东西.

Unfortunately the relational model is not generally understood (including by "relational" DBMSs), so instead these systems reject what they could simply extend.

这篇关于关系数据到非关系数据的合理导出的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-03 22:00
查看更多