blocks|key|638553|text|CMS的唯一固有特征是它将内容与显示分离。它在哪里或如何存储这些内容是任意的。连接到数据存储的机制也无关紧要。您可能认为“传统”数据库很常见，但绝不是必需的-任何数据支持都是一个包含内容的数据库-文本文件、XML、SimpleDb或Google+App+Engine等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|638554|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|$]]

The only thing inherently characteristic of a CMS is that it separates content from display. Where or how it stores that content is arbitrary. The mechanism for connecting to the data store is also of no consequence. What you might think of as a "traditional" database is common but by no means necessary - any data backing is a database of content - text files, XML, SimpleDb or Google App Engine, etc.

blocks|key|1938932|text|嗯，所有(或大多数)汽车都有四个轮子。但这并不意味着五轮车就不能是一辆车。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1938933|CMS有数据抽象是有意义的，但这并不意味着他们必须有。|1938934|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|$]]

Well, all(or most) cars have 4 wheels. But it doesn't mean a 5 wheeler cannot be a car.

It makes sense for CMS to have data abstraction, it does not mean they MUST have.

blocks|key|638504|text|我认为可以肯定地说，大多数CMS都使用DAL，但可能有一些你从未听说过的远程CMS不使用DAL，所以我不会说所有CMS都使用DAL。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|638505|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|$]]

I think it's safe to say that most CMS' use a DAL, but there's probably some remote one you've never heard of that doesn't, so I wouldn't claim that all CMS' use one.

blocks|key|1941401|text|不怎么有意思。这是好的软件设计的一个特征。经验法则是：“对接口编程，而不是实现”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1941402|我建议你掌握一个好的数据库层的诀窍，并把这些挫折抛在脑后。好的软件设计需要自律！|1941403|也许你会喜欢阅读一些设计模式和原则。稍后它将为您省去很多麻烦：http://en.wikipedia.org/wiki/Design_pattern|offset|length|1941404|祝你学习顺利！|1941405|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Design_pattern^0|0|0|V|17|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Not really. It's a characteristic of good software design. The rule of thumb is: "Program to an interface, not an implementation". 

I'd recommend getting the hang of a good db layer and pushing those frustrations to the back of your mind. Good software design takes discipline!

Maybe you might like to read up on some design patterns and principles. It will save you a lot of trouble later on: <a href="http://en.wikipedia.org/wiki/Design_pattern" rel="nofollow noreferrer">http://en.wikipedia.org/wiki/Design_pattern</a>

Good luck in your learnings!

blocks|key|744517|text|我不这么认为，Wikipedia似乎也同意我的观点。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|744518|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/List_of_Content_Management_Systems#PHP_2^0|7|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]]]]

I wouldn't say so, <a href="http://en.wikipedia.org/wiki/List_of_Content_Management_Systems#PHP_2" rel="nofollow noreferrer">Wikipedia</a> also seems to agree with me.

blocks|key|2153386|text|是的，我同意。两个主要的PHP库(Drupal和Joomla)都有某种形式的数据库抽象，即although+Drupal's+is+pretty+slim。Joomla+looks+like+it+might+have+a+little+more+to+it+than+Drupal|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2153387|entityMap|0|LINK|mutability|MUTABLE|url|http://api.drupal.org/api/group/database/6|1|http://api.joomla.org/Joomla-Framework/Database/JDatabase.html^0|19|W|0|2D|1K|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

Yes, I would agree. The 2 major PHP CMS libraries (Drupal and Joomla) each have some form of database abstraction, <a href="http://api.drupal.org/api/group/database/6" rel="nofollow noreferrer">although Drupal's is pretty slim</a>. Joomla <a href="http://api.joomla.org/Joomla-Framework/Database/JDatabase.html" rel="nofollow noreferrer">looks like it might have a little more to it than Drupal</a>.

blocks|key|2153551|text|数据库抽象层是几乎任何基于web的应用程序的特征。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2153552|这通常用于实现关注点分离：http://en.wikipedia.org/wiki/Separation_of_concerns|offset|length|2153553|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Separation_of_concerns^0|0|D|1F|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]]]]

A database abstraction layer is a characteristic of almost any web based application.

This is commonly used to accomplish Separation of Concerns:
<a href="http://en.wikipedia.org/wiki/Separation_of_concerns" rel="nofollow noreferrer">http://en.wikipedia.org/wiki/Separation_of_concerns</a>

As a php learner, I have been experimenting with some of the smaller PHP CMS'. All CMS' that I have used employ a database abstraction layer.

Am I correct in assuming that this would be a characteristic of just about all PHP CMS'?

Thanks!

Is it correct to say that virtually all CMS' have database abstraction

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

作为一名php学习者，我一直在尝试一些较小的PHP内容管理系统。我使用的所有内容管理系统都采用了数据库抽象层。我假设这将是几乎所有PHP CMS的一个特征，对吗？谢谢!

问几乎所有的CMS都有数据库抽象，这是正确的吗
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问几乎所有的CMS都有数据库抽象，这是正确的吗EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问几乎所有的CMS都有数据库抽象，这是正确的吗
EN