@lists.php.net
Subject: Re: Re: [PHP] CMS-Blog system
Thank you for all the comments.
Thanks for the WP tip: I don't know much about wordpress (it looks
good), but I have tryed enough of open-source CMS to say that they are
based on messy solutions (one for all = joomla) + it won't be free
PROTECTED]
Sent: Thursday, September 04, 2008 5:05 AM
To: php-general@lists.php.net
Subject: Re: Re: [PHP] CMS-Blog system
Thank you for all the comments.
Thanks for the WP tip: I don't know much about wordpress (it looks
good), but I have tryed enough of open-source CMS to say that they are
based
On Fri, 2008-09-12 at 11:07 +0100, Luke wrote:
don't forget that the complexity of the PHP is increased muchly with
multiple databases... Keep it simple...
You must be doing it wrong. Global $db perchance?
Cheers,
Rob.
--
http://www.interjinn.com
Application and Templating Framework for PHP
On 3 Sep 2008, at 22:01, Martin Zvarík wrote:
I am working on CMS-Blog system, which will be using approx. 10 000
users.
I have a basic question - I believe there are only two options -
which one is better?
1) having separate databases for each blog = fast
(problem: what if I will need to
On 4 Sep 2008, at 06:56, Yannick Warnier wrote:
Le mercredi 03 septembre 2008 à 22:07 +0100, Luke a écrit :
seperate databases is a hassle, since you have to mess with multiple
connections, I would go with the one database. Just cut down on data
storage, use userids instead of usernames for
Thank you for all the comments.
Thanks for the WP tip: I don't know much about wordpress (it looks
good), but I have tryed enough of open-source CMS to say that they are
based on messy solutions (one for all = joomla) + it won't be free blog
system, so I don't think using this free system
On 4 Sep 2008, at 11:04, Martin Zvarík wrote:
Thank you for all the comments.
Thanks for the WP tip: I don't know much about wordpress (it looks
good), but I have tryed enough of open-source CMS to say that they
are based on messy solutions (one for all = joomla) + it won't be
free blog
Please keep replies on the list.
On 4 Sep 2008, at 11:38, Martin Zvarík wrote:
On 4 Sep 2008, at 11:04, Martin Zvarík wrote:
Thank you for all the comments.
Thanks for the WP tip: I don't know much about wordpress (it looks
good), but I have tryed enough of open-source CMS to say that they
Le jeudi 04 septembre 2008 à 10:31 +0100, Stut a écrit :
On 4 Sep 2008, at 06:56, Yannick Warnier wrote:
Le mercredi 03 septembre 2008 à 22:07 +0100, Luke a écrit :
seperate databases is a hassle, since you have to mess with multiple
connections, I would go with the one database. Just cut
-Original Message-
From: Martin Zvarík [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 04, 2008 5:05 AM
To: php-general@lists.php.net
Subject: Re: Re: [PHP] CMS-Blog system
Thank you for all the comments.
Thanks for the WP tip: I don't know much about wordpress (it looks
Hi,
I am working on CMS-Blog system, which will be using approx. 10 000 users.
I have a basic question - I believe there are only two options - which
one is better?
1) having separate databases for each blog = fast
(problem: what if I will need to do search in all of the blogs for some
seperate databases is a hassle, since you have to mess with multiple
connections, I would go with the one database. Just cut down on data
storage, use userids instead of usernames for identification in the tables
and such.
2008/9/3 Martin Zvarík [EMAIL PROTECTED]
Hi,
I am working on CMS-Blog
On Wed, Sep 3, 2008 at 5:01 PM, Martin Zvarík [EMAIL PROTECTED] wrote:
Hi,
I am working on CMS-Blog system, which will be using approx. 10 000 users.
I have a basic question - I believe there are only two options - which one
is better?
1) having separate databases for each blog = fast
Martin Zvarík schreef:
Hi,
I am working on CMS-Blog system, which will be using approx. 10 000 users.
using them? sounds like google or M$
I have a basic question - I believe there are only two options - which
one is better?
1) having separate databases for each blog = fast
(problem:
Le mercredi 03 septembre 2008 à 22:07 +0100, Luke a écrit :
seperate databases is a hassle, since you have to mess with multiple
connections, I would go with the one database. Just cut down on data
storage, use userids instead of usernames for identification in the tables
and such.
Not only
15 matches
Mail list logo
