wow…
wp blog is a dynamic blog
that means it picks information from the database to create pages on the fly.
Using a database gives you some specific benefits. You can dump the contents of the database and have a _complete_ backup of all your data and settings, which you can then take to a different host and restore, in one fell swoop.
Using a database also allows you to fiddle with the site layout and see immediate changes. Because the data (post contents) are pulled from the database, you can change the HTML and PHP markup with tremendous ease. You can also change the amount of data displayed on pages without nassive amounts of cut-and-paste.
How about supporting other DBs like Berkeley, Post, etc.
Thread Starter
Anonymous
how about XML ?
you should give it a try!
sure, database is good, if my blog more than 1000 visitor a day..
It has a number of benefits structurally. It completely separates, the content (data) from the app (WP) from the interface (index.php) from the style (CSS).
Flat files would not do it,
Thread Starter
Anonymous
“how about XML ?
you should give it a try!
sure, database is good, if my blog more than 1000 visitor a day..”
check http://www.pivotlog.net for this
Thread Starter
Anonymous
in many countries,rental homepage services provide only cgi (perl,ruby), so they can’t install wordpress.
so I think wordpress must be able to use other databases.
why not sqlite or BerleyDB?
if wordpress can handle them,we can enclose them.
I see no real reason support for other databases couldn’t be added. Simply define all the database calls as wrapper functions and then include one file that contains database-specific definitions of these wrappers. Make the specific database used configurable via wp-config.php before installation and you’d be good to go.
I don’t know how spread out the database calls are so I’m not sure how feasible it is to import one DB-specific file for all database calls, but I can’t think of a technical reason it couldn’t be done. Anyways, tho I’ve never used it isn’t this what require_once was designed to do?
(Personally, I’m kinda hoping for SQLite support if anything’s added. Everything else is usually extra when getting hosting, but for any host that offers PHP5 when it becomes ubiquitous it’ll be free. There’s also the plus of easy DB export.)
1539
How did you come to the conclusion that SQLite is standard and MySQL is “extra”? The majority of hosts I’ve seen that support databases offer MySQL.
1. MySQL is a pretty standard service offered by hosting companies at this point… well, at least on linux hosting, but on lots of windows hosts too (since it runs on either OS, and it doesn’t actually have to run, or should be run, on the webserver boxes anyway…).
2. In the cases where it isn’t, they likely aren’t running the latest PHP releases, and thus wouldn’t have SQLLite. SQLLite is a new embedded SQL system built into the new PHP5 (I believe), that emulates a full SQLServer through the local filesystem.
3. In the case you need support for a different implementation, wpdb.php generally encapsulates all the interfacing with the database, except for:
a. badly written code (imho),
b. code written with another abstraction layer above wpdb (like my CG-Amazon and CG-Referer systems do), but still going through wpdb IF on a WP site (otherwise has default mysql direct implementation capabilities).
Other DBs could be implemented. But aside from SQLLite, which might be interesting for more embedded applications (i.e., you don’t have a DB server around, nor ability to add one), trying to really add support for other DBs I think falls outside the realm of what WP needs to focus on. There are MUCH bigger feature areas that need to be worked on…
-d
CHAITGEAR
SQLite will be built into PHP5 by default (according to the PHP manual page). It will require a custom install to not have it. PHP has hooks for MySQL, but MySQL is separate. Hosting with a real database such as MySQL usually costs a little extra beyond the cost of hosting with PHP. If your database needs are minimal, SQLite will work just as well as MySQL, and it will be free while MySQL will be extra.
PHP5 isn’t even out now in a real release, but it will be adopted, if slowly (I’ll give it a couple years to be prevalent). When it’s adopted enough that SQLite is common with PHP, for minimal database needs there will be few reasons to use MySQL over SQLite.
Of course, I’m assuming most hosts won’t go to the effort to compile PHP5 without SQLite. I have no knowledge of web host practices in this regard, so perhaps I’m wrong there.
I also never suggested supporting other databases was a pressing concern. MySQL is prevalent now, so until the list of big features to implement is exhausted there’s no real reason to add support for any other database.
