On Thu, May 16, 2002 at 11:32:48AM -0400, Lance Lovette wrote:
> I have partitioned my data such that each client has its own
> database (clientdb1, clientdb2, ... clientdbN). All the databases
> have the same structure (same tables, columns, etc.). This design
> works great except for one caveat
I have partitioned my data such that each client has its own database
(clientdb1, clientdb2, ... clientdbN). All the databases have the same
structure (same tables, columns, etc.). This design works great except for
one caveat - when I make a change to the database structure I have to make
the sam
what you are looking for.
Tom Haapanen
[EMAIL PROTECTED]
-Original Message-
From: Joe [mailto:[EMAIL PROTECTED]]
Sent: 22 October 2001 02:04
To: [EMAIL PROTECTED]
Subject: Database Structures
Hello,
Hi, I need some help on something here. I need to know the best way to set
up this data
[EMAIL PROTECTED]
-Original Message-
From: Steve Meyers [mailto:[EMAIL PROTECTED]]
Sent: 22 October 2001 03:27
To: Joe; [EMAIL PROTECTED]
Subject: RE: Database Structures
Creating a new table per image isn't unheard of -- at a company I used to
work for, we estimated that we had arou
> I have a site with a bunch of images/reviews. What i want is for
> registered
> users to rate and leave reviews themselves. I'm not sure how I should set
> up this database though.
>
> Now, I have a table that holds the user info. Should I create a new table
> for each image, which holds th
Hello,
Hi, I need some help on something here. I need to know the best way to set
up this database.
I have a site with a bunch of images/reviews. What i want is for registered
users to rate and leave reviews themselves. I'm not sure how I should set
up this database though.
Now, I have a tab
