Matter of preference really. Do you put all your files in one directory? I
do for the most part, but when it comes to security you can divy out access
to different databases rather than each table and it makes things simpler,
so I use different databases for different projects. Also, I think
That all really depends on you. I would certainly say that, in general,
any given database should only have one users table (with a separate
table holding roles, permissions, etc.) In all likelihood - if all of
these systems will be working together within a single company, and be
built in a
On Mon, 18 Oct 2004 14:53:41 -0500, Norland, Martin
[EMAIL PROTECTED] wrote:
That all really depends on you. I would certainly say that, in general,
any given database should only have one users table (with a separate
table holding roles, permissions, etc.) In all likelihood - if all of
: Re: [PHP-DB] how many databases should I create
.. chop ..
shouldn't a good rdbms take care of that though (with reasonable
security measures)? can't you get fine grained user privs, at least
with a proper db? postgres? Cheers Antoine
--
PHP Database Mailing List (http://www.php.net
preference for MY application, just airing my
thoughts
Graham
-Original Message-
From: Norland, Martin [mailto:[EMAIL PROTECTED]
Sent: 18 October 2004 22:12
To: [EMAIL PROTECTED]
Subject: RE: [PHP-DB] how many databases should I create
You're talking two different users here - in my
