Think about how your going to make backups.
1) Would you backup one database with all the mailing lists together ?
2) Would you keep the backups of each user separate ?
3) Could users ask you to restore mailing lists from the past ?
You could make one mysqldump for everybody from one database if
I'd never have a separate database for everyone or even a separate table
for everyone. Here's a rough idea of how I'd do it
mysql CREATE TABLE customer (
- `custid` INT NOT NULL AUTO_INCREMENT,
- `lastname` VARCHAR(25) not null,
- `firstname` VARCHAR(25) NOT NULL,
- PRIMARY
On 8/23/07, Jason Pruim [EMAIL PROTECTED] wrote:
I am planning on having the database open to customers of mine to
store their mailing addresses on-line, and be able to manage the
records.
Is it safe, to have 1 database with lots of tables? Or am I safer
setting up separate databases for
On Aug 23, 2007, at 11:44 AM, Gary Josack wrote:
I'd never have a separate database for everyone or even a separate
table for everyone. Here's a rough idea of how I'd do it
mysql CREATE TABLE customer (
- `custid` INT NOT NULL AUTO_INCREMENT,
- `lastname` VARCHAR(25) not null,
-
On Aug 23, 2007, at 11:28 AM, Rolando Edwards wrote:
Think about how your going to make backups.
1) Would you backup one database with all the mailing lists together ?
If I went the route of 1 database, Many tables, I would just backup
the entire database and all the tables in one shot.
On Aug 23, 2007, at 11:50 AM, David T. Ashley wrote:
On 8/23/07, Jason Pruim [EMAIL PROTECTED] wrote:
I am planning on having the database open to customers of mine to
store their mailing addresses on-line, and be able to manage the
records.
Is it safe, to have 1 database with lots of
On 8/23/07, Jason Pruim [EMAIL PROTECTED] wrote:
b)Terminating TCP connections and ensuring that each PHP script
runs to
completion, anyway, and that the database isn't left in an
indeterminate
state due to this.
Dave.
What do you mean by b? If all the connections come from the
Personally, I think I'd go with one DATABASE per customer. That way the your
code would be the same, and easier to handle. It would be easier to manage
the security at the database level, I suspect. I'd set up a ../inc directory
outside the web server root that would have one file per customer,
I concur. Also it makes it easier to remove a customer if they leave.
Finally your backups will only lock up one customer's database at time and
for a much shorter period.
On Thu, August 23, 2007 10:50, Jerry Schwartz said:
Personally, I think I'd go with one DATABASE per customer. That way
